[JIRA] (JENKINS-39119) Can't lock nodes between stages
Title: Message Title Reinhold Füreder commented on JENKINS-39119 Re: Can't lock nodes between stages I may not understand your requirements correctly, but I think the "Lockable Resources" plugin (you are mentioning) should (now) allow you what you need/want according to: https://jenkins.io/blog/2016/10/16/stage-lock-milestone/ https://wiki.jenkins-ci.org/display/JENKINS/Lockable+Resources+Plugin Because these "resources" are created automa(t|g)ically in pipelines? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33847) Support for implicit variable WORKSPACE in Pipeline stages
Title: Message Title
Reinhold Füreder commented on JENKINS-33847
Re: Support for implicit variable WORKSPACE in Pipeline stages
I am not sure if I understand your requirement correctly, but maybe pwd() and/or withEnv(...) pipeline steps can be used?
withEnv(['WORKSPACE=pwd()']) {
// some block
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36451) Repository Browser URL not saved in Project Pipeline Configuration
Title: Message Title Reinhold Füreder commented on JENKINS-36451 Re: Repository Browser URL not saved in Project Pipeline Configuration clausfod Since in our case SVN is affected too, I would hope it is not the "git-plugin" component that is to blame? (I must admit though that the git plugin would be installed in our case too) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32744) Svn revisions not showing up in pipeline build
Title: Message Title Reinhold Füreder commented on JENKINS-32744 Re: Svn revisions not showing up in pipeline build Oh! Actually there are some intermediate builds that do not have any SVN changes (manual triggered builds IIRC) and then the SVN revision information is really NOT displayed in the build status page. Which, hm, might be an acceptable behaviour (kind of "works as expected/designed"), although one could also desire to always show it. (Considering the huge number of open subversion plugin issues, I might encourage you to maybe resolve this issue with e.g. "won't do" or "not a defect" or so?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32744) Svn revisions not showing up in pipeline build
Title: Message Title Reinhold Füreder commented on JENKINS-32744 Re: Svn revisions not showing up in pipeline build Sorry Jon Sten, I was not reading carefully enough. However, what I just saw in my local environment (latest versions of everything, e.g. Jenkins 2.40) is that the SVN revision is NOT shown "only" for the first pipeline build, but seemingly for all subsequent ones. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32744) Svn revisions not showing up in pipeline build
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-32744 Svn revisions not showing up in pipeline build Change By: Reinhold Füreder Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32744) Svn revisions not showing up in pipeline build
Title: Message Title Reinhold Füreder commented on JENKINS-32744 Re: Svn revisions not showing up in pipeline build While "/job//pipeline-syntax/globals" at least documents that, I also think this should be fixed, if possible: Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39487) SVN changesets duplicated when using multibranch pipeline
Title: Message Title Reinhold Füreder commented on JENKINS-39487 Re: SVN changesets duplicated when using multibranch pipeline Maybe it is not only related to JENKINS-38204, but even a duplicate? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40157) Subversion checkout it not working
Title: Message Title Reinhold Füreder resolved as Not A Defect I think Jon is right and also dare to resolve this issue with "not a defect" (because I was shocked by the huge number of open svn plugin issues; and so some clean-up of non-defects might be benefitial...) Jenkins / JENKINS-40157 Subversion checkout it not working Change By: Reinhold Füreder Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-23941) SVN post commit hook does not rsolve jobs to build
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-23941
Re: SVN post commit hook does not rsolve jobs to build
Because we are currently experiencing the same ( \ ?) problem (using Jenkins v2.36 and Subversion Plugin v2.71) :Would that ("Jenkins logs that the notification has been received but that there is no job interested in the change.") look like this:{noformat}Dez 15, 2016 3:16:46 PM jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotifyINFO: Received post-commit hook from fa86427e-e420-4d14-a4fd-9ab1bdfcde57 for revision 119.196 on paths [...] // value is correctDez 15, 2016 3:16:46 PM jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotifyINFO: No subversion consumers for UUID fa86427e-e420-4d14-a4fd-9ab1bdfcde57{noformat}Or like mentioned in here: https://groups.google.com/forum/#!topic/jenkinsci-users/FGTaADCc29U
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23941) SVN post commit hook does not rsolve jobs to build
Title: Message Title
Reinhold Füreder commented on JENKINS-23941
Re: SVN post commit hook does not rsolve jobs to build
Because we are currently experiencing the same problem: Would that ("Jenkins logs that the notification has been received but that there is no job interested in the change.") look like this:
Dez 15, 2016 3:16:46 PM jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify
INFO: Received post-commit hook from fa86427e-e420-4d14-a4fd-9ab1bdfcde57 for revision 119.196 on paths [...] // value is correct
Dez 15, 2016 3:16:46 PM jenkins.scm.impl.subversion.SubversionSCMSource$ListenerImpl onNotify
INFO: No subversion consumers for UUID fa86427e-e420-4d14-a4fd-9ab1bdfcde57
Or like mentioned in here: https://groups.google.com/forum/#!topic/jenkinsci-users/FGTaADCc29U
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36451) Repository Browser URL not saved in Project Pipeline Configuration
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-36451
Re: Repository Browser URL not saved in Project Pipeline Configuration
Presumably we have the same symptom here: SVN + WebSVN2.3.3 repository browser in Jenkins Pipeline.However, the entered (in the configuration dialog) SVN repository browser URL is correctly persisted to "config.xml":{code:xml} https://svn.example.com/websvnhttps://svn.example.com/websvn {code}But maybe not used/loaded correctly anymore: when re-opening the configuration dialog, it again is set to "Auto" .Please note: Using the same settings for an "old" freestyle jobs works fine: they are not only persisted, but also shown in configuration dialog after re-opening and the changes tab shows working links to WebSVN.(Currently using newest versions of everything, e.g.: Jenkins v2.36, Subversion Plugin v2.7.1, ...)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36451) Repository Browser URL not saved in Project Pipeline Configuration
Title: Message Title Reinhold Füreder commented on JENKINS-36451 Re: Repository Browser URL not saved in Project Pipeline Configuration Presumably we have the same symptom here: SVN + WebSVN2.3.3 repository browser in Jenkins Pipeline. However, the entered (in the configuration dialog) SVN repository browser URL is correctly persisted to "config.xml": "hudson.plugins.websvn2.WebSVN2RepositoryBrowser" plugin="WebSVN2@0.9"> https://svn.example.com/websvn https://svn.example.com/websvn But maybe not used/loaded correctly anymore: when re-opening the configuration dialog, it again is set to "Auto" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
