• Content count

  • Joined

  • Last visited

  • Days Won


Misieq last won the day on October 10 2016

Misieq had the most liked content!

Community Reputation

16 Good

About Misieq

  • Rank
    Advanced Member

Recent Profile Visitors

2,681 profile views
  1. Hello Recently we have started to use Jenkins Pipelines in more excesive way. I have currently two observations regarding PlasticSCM: 1) If Pipeline script is taken from repository (e.g. Jenkinsfile) than workspace always gots delated and re-created (probably because at first Jenkins is recreating workspace to "script" folder - to checkout Jenkinsfile and later on back to regular one) 2) It is possible to configure Pipeline to checkout Jenkins file from PlasticSCM repository (PlasticSCM appears on dropdown list). However when job is already configured and you want to reconfigure it only Git and Subversion are seen at job configuration page (current configuration with PlasticSCM is not displayed but is preserved if you do not press Save/Apply).
  2. From my side just a comment/remark. In my opinion PlasticSCM SHALL remove files from workspace when switching to changeset without revisions of such files. In other case it may happen than switching between changesets result with unupdated workspace - and that is not good.
  3. Good that it is at least possible from CLI. However if you work with new GUI it would be nice to such option to context menu of changeset Of course nothing critical - but would be nice to have.
  4. Hello Could you please tell me how to create in GUI top-level branch which will not start from last changeset of /main (or any other) branch? I tried to add new top-level branch to my repo but it looks that this option is available only in menu which shows after righ-clicking at any branch. And in such case new branch is alwayes starting from the last changeset of clicked branch. Thus creation of complately new top-level branch from middle of /main or even from beginning of /main looks to be not possible (at least from GUI - I did not investigate if it is possible from CLI). Could you please add support for such case?
  5. Just a hint which have just come to my mind Possible improvement for Jenkins plugin could be to have some configuration section in "Manage Jenkins"... This configuration could detect presense of conf file in path for jenkins user conext. SImpler option - just display kind of warning with info that client configuration is missing and some hints how to create them manualu Advanced option - parse content of the file and display setting directly in Jenkins with the ability to change them and put back to xml automaticaly by plugin.
  6. Hello I know that you are focused on 6.0 branch right now, but any progress with this issue? It was reported year and the half ago.
  7. Just checked PlasticSCM Jenkins plugin v2.8 Looks that 'cm' steps now works fine (however no deep testing - just plugin installetion and single checkout). Thanks for your effort.
  8. Hi manu It's just to remind you that I am here and still waiting. Will Codice make me a present for Christmas? Regards
  9. I have just noticed that there is new version of Jenkins plugin (2.7). As stated in release notes it shall fix workspace deletion when parametrized selector is used. I have just tested it and it looks to be working fine Thanks a lot for this fix. PS. Now just pipeline support and I will have no more remarks for this plugin And yes, I confirm I have seen one of blogposts with workaround to use GitServer feature.
  10. Hi Issue title display displayed together with branch name is available in Plastic since a while... Check if you have this option set The only limitation is that for very short branches (e.g. with single changset) sometimes title is "shortened" too much.
  11. Hello It's far more than year since problem was signaled. Is there any progres with fix implementation? When could it be expected? Issue affects a lot permissions setting in my environment.
  12. Hello Is there any progress on this point? In release notes nothing is mentioned.
  13. I think that formally system does not need to determine if repository and/or server is the same. As far as I recall with GUI it is possible to just switch workspace to any repo on any server, isn't it? So maybe it would be just enough to check (in case of "use update") that physical path and name of workspace is still the same as for previous build.
  14. Hi I think you did not catch exactly my use case. I am using PARAMETRIZED SELECTOR. So my Jenkins Job has following configuration: 1) String Parameter named branch added with default value "/main" 2) Selector defined as: First build (with branch parameter set to /main) of this job (when no workspace is yet created) generates following output (behaviour correct): Building in workspace c:\j\workspace\Tutorial [tutorial] $ cm lwk --format={0}#{1}#{2} [tutorial] $ cm mkwk tutorial c:\j\workspace\Tutorial\tutorial --selector=c:\j\workspace\Tutorial\tutorial\selector4578542194289647674.txt Workspace tutorial has been correctly created [tutorial] $ cm update c:\j\workspace\Tutorial\tutorial Second build (again with branch parameter set to /main) - behaviour is correct (workspace is only updated not recreated): Building in workspace c:\j\workspace\Tutorial [tutorial] $ cm lwk --format={0}#{1}#{2} tutorial#DL1T3B5Y1#c:\j\workspace\Tutorial\tutorial [tutorial] $ cm ss wk:tutorial Selector for workspace tutorial: repository "tutorial@uskoaa37.northamerica.delphiauto.net:8087" path "/" smartbranch "/main" [tutorial] $ cm update c:\j\workspace\Tutorial\tutorial Third build (this time I have changed branch parameter value to /main/j_TUT-210) - workspace is recreated (behaviour is not correct). Building in workspace c:\j\workspace\Tutorial Deleting workspace as the configuration has changed since the last build on this computer. [tutorial] $ cm lwk --format={0}#{1}#{2} tutorial#DL1T3B5Y1#c:\j\workspace\Tutorial\tutorial [tutorial] $ cm rmwk wk:tutorial The workspace tutorial has been deleted. [tutorial] $ cm mkwk tutorial c:\j\workspace\Tutorial\tutorial --selector=c:\j\workspace\Tutorial\tutorial\selector5342539367101548308.txt Workspace tutorial has been correctly created [tutorial] $ cm update c:\j\workspace\Tutorial\tutorial
  15. Hello I have checked it with newest version of plugin. It still behaves in the same way. As previously in build log following line appears: I am still thinking that "path" which I pointed in one of the previous posts is the main root cause of such behaviour.