Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Evgeny last won the day on May 18

Evgeny had the most liked content!

Community Reputation

2 Neutral

About Evgeny

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you. I will setup all build process first, using shell. And in a few days i will check that workaround.
  2. I added all paths to the Agent Path variable and cm began to work trough the shell. It worth mentioning, that you can't add just Plastic path, as it will replace all other paths and event "sh" wouldn't be found. But cm command from Jenkins Plugin are still failing with the same error.
  3. Jenkins server is running on Windows and i'm trying to setup agent on MacOS. So i can't use absolute path to cm - that will brake all windows builds. What i tryed - Reinstall Plastic under Jenkins user (Should'n this add cm to Path?) - Add Plastic to /etc/paths /usr/local/bin /usr/bin /bin /usr/sbin /sbin /Applications/PlasticSCM.app/Contents/MonoBundle And it didn't work bizon:TestScripts jenkins$ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Applications/Xamarin Workbooks.app/Contents/SharedSupport/path-bin bizon:TestScripts jenkins$ sudo open /etc/paths - I tryed to execute cm in Bash (under Jenkins user) and it works. It seems, that cm is added to Path, but it only visible from Bash. And not visible from scripts.
  4. Maybe i did something wrong on the mac? I just did another test. Shell script executed from Jenkins pipeline "cm worspace create ..." returned "cm: command not found" [Pipeline] sh + cm workspace create hc-smf-living-pictures-client /Volumes/LittleBigBOSS/JA1/workspace/hc-smf/hc-smf-living-pictures-client/hc-smf-living-pictures-client --repository=hc-smf/hc-smf-living-pictures-client@__@cloud /Volumes/LittleBigBOSS/JA1/workspace/hc-smf/hc-smf-living-pictures-client@tmp/durable-62867457/script.sh: line 1: cm: command not found I copyed the same command in bash and executed it manually and worspace was succesfully created bizon:TestScripts jenkins$ cm workspace create hc-smf-living-pictures-client /Volumes/LittleBigBOSS/JA1/workspace/hc-smf/hc-smf-living-pictures-client/hc-smf-living-pictures-client --repository=hc-smf/hc-smf-living-pictures-client@__@cloud Workspace hc-smf-living-pictures-client has been correctly created What am i missing?
  5. I'm trying to setup iOS build on MacOS and checkout are failing with following error [TestScripts] $ cm lwk --format={wkname}#{path}#{wkid} FATAL: Cannot run program "cm" (in directory "/Volumes/LittleBigBOSS/JA1/workspace/TestJobs/TestScripts"): error=2, No such file or directory Pipeline script is very simple and it works if i launch it on Windows Node node('iOS') { cm branch: context.BranchName, repository: context.SCMRepository, server: context.SCMServer } I checked all steps manually and they works. cd to the path "/Volumes/LittleBigBOSS/JA1/workspace/TestJobs/TestScripts" launched command "cm lwk --format={wkname}#{path}#{wkid}" Here are shell log for this: Last login: Fri May 15 23:28:59 on ttys000 bizon:~ admin$ cd /Volumes/LittleBigBOSS/JA1/workspace/TestJobs/TestScripts bizon:TestScripts admin$ cm lwk --format={wkname}#{path}#{wkid} default#/Users/admin/wkspaces/default#8b1b592b-f895-4377-b118-d4f1fa7fcbd0 bizon:TestScripts admin$ PS Noticed, that i previously opened shell from admin user. Repeated test, using Jenkins user with same results
  6. As i said earlier - i solved my problem by defining 2 different libraries in Jenkins Settings. I'm ok with this workaround. So we can close this topic In case, you want to investigate this further: version selection doesn't work as they propose in the previous link for legacy SCM. I tested it with: - Plastic - returns errors in selector - Github (legacy SCM) - just checksout latest changeset (regardless of brunch) I didn't find any references to someone using library versions on legacy SCM and decided that this is a Jenkins bug, but i didn't created issue on their bug tracker
  7. I read this article before. In case of git - it works with tags and only if you use "Modern scm". There are no options for Plastic in "Modern scm". And in "Legacy scm" you only option is to use "${library.Default.version}". And it didn't work even in GIT.
  8. Yes, in that case all works well. But how do you select library varsion that way? For example: @Library('myrepo@development') _ @Library('myrepo@v1.0') _ @Library('myrepo@stable') _ etc
  9. I tryed the same setup with GitHub and it didn't work either. It just checkout the latest changeset. So it looks like some bug in Jenkins. I added 2 different libraries that point to a different branches of the same repository. So now i can't use "Load implicitly" setting, but i can switch shared library on certain jobs to development branch.
  10. I tryed "echo ${library.Default.version}" and get an error hudson.remoting.ProxyException: groovy.lang.MissingPropertyException: No such property: library for class: WorkflowScript
  11. Hi, I'm currently trying to setup shared libraries to use different versions. Example use-case: Test job, that will use /main/development branch, where i can experiment with shared libraries and not ruining all production jobs. 1) First of all i tryed to set branch explicitly to "/main/development": It works, as expected. But i can't see this selector in Jenkins log. Log looks loke this, and only in changesets i can see, that new selector actually worked 2) After that a tryed to setup lybrary versions for legacy SCM, as described in documentation (https://www.jenkins.io/doc/book/pipeline/shared-libraries/) Here are shared libraries settings: Build fails with the same error. I tryed: - Default version = "/main" - Default version = "/main/development" - @Library('Default@main/development') in pipeline script Maybe i'm making some stupid error in setup, but i have no means to debug that, as i can't get final selector from log. Log shows only last succesful selector, and that new selector are saved to txt file, that instantly gets deleted. I checked, that both selectors ("/main" and "/main/development"), written explicitly in settings - works as expected. But "${library.Default.version}" shows an error. What i'm doing wrong? Or how i can see actual selector, that are generated in txt file?
  12. Never mind, i decided not to use this plugin. Shared libraries work fine with Plastic!
  13. I'm not using shared libraries. This plugin has his analogy of shared libraries. I'm using PlasticSCM Plugin 3.3
  14. I think, i run into the same problem with Templating Engine plugin for Jenkins. https://plugins.jenkins.io/templating-engine/ In "Configure System" you can set 2 repositories: 1) Pipeline Configuration - works fine with Plastic 2) Library Sources - don't work with plastic, but works ok with GIT. Any ideas?
  15. Run into the same problem. It works, but you need to change permissions on client.conf, or Plastic would not have permission to access this file.
  • Create New...