[JIRA] (JENKINS-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title Johnny Willemsen commented on JENKINS-54225 Re: Using disableDeferredWipeout within pipeline job results in no deleted workspace Shouldn't the plugin set deleteDirs to true in case we do a deferred delete? Or at least have some documentation extensions to mention this, this is confusing for people who think they just disable the async delete and get strange errors due to that Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title Johnny Willemsen commented on JENKINS-54225 Re: Using disableDeferredWipeout within pipeline job results in no deleted workspace I can confirm that adding deleteDirs solved the issue of the partial delete. As workaround on Windows we use `rm -rf` from MinGW, it looks that we have some files in the workspace which are still in use in some builds, rm can remove them without problems, with get the error below, is there a forced delete options (... is a full path) ERROR: Cannot delete workspace :Unable to delete '...ACE_ETCL_Parserd.dll’. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. Error when executing always post condition: hudson.AbortException: Cannot delete workspace: Unable to delete '...\ACE_ETCL_Parserd.dll’. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. at hudson.plugins.ws_cleanup.WsCleanup.perform(WsCleanup.java:244) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title Johnny Willemsen commented on JENKINS-54225 Re: Using disableDeferredWipeout within pipeline job results in no deleted workspace Did several builds today with 'deleteDirs' added and it seems to work, this night a lot more builds will run but it looks you found the cause Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55047) Failed to get _links error when opening blueocean
Title: Message Title
Johnny Willemsen updated an issue
Jenkins / JENKINS-55047
Failed to get _links error when opening blueocean
Change By:
Johnny Willemsen
When opening the blueocean for the full jenkins server we get the errors below and the main blueocean page just says loading and no pipelines are shown. For a single pipeline it does work . fc12_ceel_x86_64_debug is a very old job which has been removed from jenkins a long time ago, maybe some artifact left on disk, not sure. {code:java}Dec 06, 2018 9:34:44 AM WARNING io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1 getValueFailed to get "_links" from a io.jenkins.blueocean.service.embedded.rest.FreeStylePipeline$FreeStyleRunSummaryio.jenkins.blueocean.commons.ServiceException$NotFoundException: Run 2013-10-21_19-05-09 not found in organization jenkins and pipeline fc12_ceel_x86_64_debug at io.jenkins.blueocean.service.embedded.rest.RunContainerImpl.get(RunContainerImpl.java:72) at io.jenkins.blueocean.service.embedded.rest.RunContainerImpl.get(RunContainerImpl.java:40) at io.jenkins.blueocean.service.embedded.LinkResolverImpl.resolveRun(LinkResolverImpl.java:63) at io.jenkins.blueocean.service.embedded.LinkResolverImpl.resolve(LinkResolverImpl.java:42) at io.jenkins.blueocean.rest.hal.LinkResolver.resolveLink(LinkResolver.java:32) at io.jenkins.blueocean.service.embedded.rest.AbstractRunImpl.getLinks(AbstractRunImpl.java:356) at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:72)Caused: java.lang.reflect.InvocationTargetException at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:74) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.getValue(Export.java:167) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:303) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:154) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199) at io.jenkins.blueocean.commons.stapler.Export.writeOne
[JIRA] (JENKINS-55047) Failed to get _links error when opening blueocean
Title: Message Title Johnny Willemsen created an issue Jenkins / JENKINS-55047 Failed to get _links error when opening blueocean Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-12-06 08:40 Environment: Jenkins 2.138.3 Priority: Minor Reporter: Johnny Willemsen When opening the blueocean for the full jenkins server we get the errors below and the main blueocean page just says loading and no pipelines are shown. For a single pipeline it does work Dec 06, 2018 9:34:44 AM WARNING io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1 getValue Failed to get "_links" from a io.jenkins.blueocean.service.embedded.rest.FreeStylePipeline$FreeStyleRunSummary io.jenkins.blueocean.commons.ServiceException$NotFoundException: Run 2013-10-21_19-05-09 not found in organization jenkins and pipeline fc12_ceel_x86_64_debug at io.jenkins.blueocean.service.embedded.rest.RunContainerImpl.get(RunContainerImpl.java:72) at io.jenkins.blueocean.service.embedded.rest.RunContainerImpl.get(RunContainerImpl.java:40) at io.jenkins.blueocean.service.embedded.LinkResolverImpl.resolveRun(LinkResolverImpl.java:63) at io.jenkins.blueocean.service.embedded.LinkResolverImpl.resolve(LinkResolverImpl.java:42) at io.jenkins.blueocean.rest.hal.LinkResolver.resolveLink(LinkResolver.java:32) at io.jenkins.blueocean.service.embedded.rest.AbstractRunImpl.getLinks(AbstractRunImpl.java:356) at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:72) Caused: java.lang.reflect.InvocationTargetException at io.jenkins.blueocean.commons.stapler.export.
[JIRA] (JENKINS-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title
Johnny Willemsen edited a comment on JENKINS-36322
Re: NaN execution time may appear if a stage gets terminated incorrectly
Also NaNy NaNd is shown for a pipeline which has a step with an _expression_, use the following pipeline job, just update label to match something in your jenkins {noformat}String foopipeline foopipeline {agent { node {label 'fc29' }} stages { stage('Create postbuild.sh') {when { _expression_ { foo == "bar" }}steps { writeFile file: 'postbuild.sh', text: "bar"} } }}{noformat}{{!Screenshot_20181119_161957.png|thumbnail!}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title
Johnny Willemsen edited a comment on JENKINS-36322
Re: NaN execution time may appear if a stage gets terminated incorrectly
Also NaNy NaNd is shown for a pipeline which has a step with an _expression_, use the following pipeline job, just update label to match something in your jenkins {quote} { { noformat } } String foopipeline foopipeline { agent { node { label 'fc29' } } stages { stage('Create postbuild.sh') { when { _expression_ \ { foo == "bar" } } steps { writeFile file: 'postbuild.sh', text: "bar" } } }} { quote noformat }{{!Screenshot_20181119_161957.png|thumbnail!}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title
Johnny Willemsen edited a comment on JENKINS-36322
Re: NaN execution time may appear if a stage gets terminated incorrectly
{{ Also }} NaNy NaNd is shown for a pipeline which has a step with an _expression_, use the following pipeline job, just update label to match something in your jenkins {quote} {{ String foo }} {{ String foo pipeline { }} {{ agent { }} {{ node { }} {{ label 'fc29' }} {{ } }} {{ } }} {{ stages { }} {{ stage('Create postbuild.sh') { }} {{ when { }} {{ _expression_ \{ foo == "bar" } }} {{ } }} {{ steps { }} {{ writeFile file: 'postbuild.sh', text: "bar" } } {{ } }} {{ } }} {{ } }} { { quote } }} {{!Screenshot_20181119_161957.png|thumbnail!}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title
Johnny Willemsen commented on JENKINS-36322
Re: NaN execution time may appear if a stage gets terminated incorrectly
{{Also }}NaNy NaNd is shown for a pipeline which has a step with an _expression_, use the following pipeline job, just update label to match something in your jenkins String foo pipeline { agent { node { label 'fc29' {{ }}} {{ }}} stages { {{ stage('Create postbuild.sh') {}} {{ when {}} {{ _expression_ { foo == "bar" }}} {{ }}} {{ steps {}} {{ writeFile file: 'postbuild.sh', text: "bar"}} {{ }}} {{ }}} {{ }}} }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title Johnny Willemsen updated an issue Jenkins / JENKINS-36322 NaN execution time may appear if a stage gets terminated incorrectly Change By: Johnny Willemsen Attachment: Screenshot_20181119_161957.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title
Johnny Willemsen updated an issue
Jenkins / JENKINS-54225
Using disableDeferredWipeout within pipeline job results in no deleted workspace
Change By:
Johnny Willemsen
We are using pipeline and at the end of the pipeline we have a stage as below. We added the disableDeferredWipeout recently to make sure that all disk space of the workspace is reclaimed before the job ends. We now notice that the workspace is not deleted anymore, when we remove the disableDeferredWipeout the workspace directory is gone again. Have tried to find some logs but can't find anything.{{stage('Post cleanup') {}}{{step([$class: 'WsCleanup', disableDeferredWipeout: true])}}{{}}}In the log we only get the message below but at the end the workspace is still there{{[WS-CLEANUP] Deleting project workspace...}} {{[WS-CLEANUP] Deferred wipeout is disabled by the job configuration...}} {{[WS-CLEANUP] done}} As reproducer you can use the pipeline job below, only adapt the node argument. After the pipeline job has finished we would expect to have an empty workspace but with disableDeferredWipeout:true the buildtools directory is still there, without the argument the workspace is deleted {{ node('Scarab_fc28_x86_64_01') { }} {{ stage('Pre cleanup') { }} {{ cleanWs() }} {{ } }} {{ stage('Buildtools checkout') { }} {{ dir ('buildtools') { }} {{ git changelog: false, poll: false, url: 'https://github.com/DOCGroup/MPC', shallow: true }} {{ } }} {{ } }} {{ stage('Post cleanup') { }} {{ cleanWs disableDeferredWipeout:true }} {{ // cleanWs() }} {{ } }} {{ } }}
Add Comment
[JIRA] (JENKINS-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title
Johnny Willemsen updated an issue
Jenkins / JENKINS-54225
Using disableDeferredWipeout within pipeline job results in no deleted workspace
Change By:
Johnny Willemsen
We are using pipeline and at the end of the pipeline we have a stage as below. We added the disableDeferredWipeout recently to make sure that all disk space of the workspace is reclaimed before the job ends. We now notice that the workspace is not deleted anymore, when we remove the disableDeferredWipeout the workspace directory is gone again. Have tried to find some logs but can't find anything.{{stage('Post cleanup') {}}{{step([$class: 'WsCleanup', disableDeferredWipeout: true])}}{{}}}In the log we only get the message below but at the end the workspace is still there{{[WS-CLEANUP] Deleting project workspace...}}{{[WS-CLEANUP] Deferred wipeout is disabled by the job configuration...}}{{[WS-CLEANUP] done}} As reproducer you can use the pipeline job below, only adapt the node argument. After the pipeline job has finished we would expect to have an empty workspace but with disableDeferredWipeout:true the buildtools directory is still there, without the argument the workspace is deleted{{node('Scarab_fc28_x86_64_01') {}}{{ stage('Pre cleanup') {}}{{ cleanWs()}}{{ }}}{{ stage('Buildtools checkout') {}}{{ dir ('buildtools') {}}{{ git changelog: false, poll: false, url: 'https://github.com/DOCGroup/MPC', shallow: true}}{{ }}}{{ }}} {{ stage('Post cleanup') {}}{{ cleanWs disableDeferredWipeout:true}}{{// cleanWs()}}{{ }}}{{}}}
Add Comment
[JIRA] (JENKINS-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title Johnny Willemsen updated an issue Jenkins / JENKINS-54225 Using disableDeferredWipeout within pipeline job results in no deleted workspace Change By: Johnny Willemsen Environment: wsCleanup 0.36 and Jenkins ver. 2.138.2Jenkins node is Fedora 28 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title
Johnny Willemsen created an issue
Jenkins / JENKINS-54225
Using disableDeferredWipeout within pipeline job results in no deleted workspace
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
ws-cleanup-plugin
Created:
2018-10-24 17:34
Priority:
Minor
Reporter:
Johnny Willemsen
We are using pipeline and at the end of the pipeline we have a stage as below. We added the disableDeferredWipeout recently to make sure that all disk space of the workspace is reclaimed before the job ends. We now notice that the workspace is not deleted anymore, when we remove the disableDeferredWipeout the workspace directory is gone again. Have tried to find some logs but can't find anything. stage('Post cleanup') { step([$class: 'WsCleanup', disableDeferredWipeout: true]) } In the log we only get the message below but at the end the workspace is still there [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [WS-CLEANUP] done
Add Comment
[JIRA] (JENKINS-35026) Pipeline script from SCM triggers builds on sub pipeline change
Title: Message Title Johnny Willemsen edited a comment on JENKINS-35026 Re: Pipeline script from SCM triggers builds on sub pipeline change I am attaching a text file with* jenkins job that pulls the pipeline script from scm, job is triggered on a schedule but the repo repository we get the script from isn't pulled* the contents of the script, have to us two repositories to get the same, the jenkins-jobs git repo is the same as we get the script from* the result of a poll, we had a chagne change in jenkins-jobs, but that shouldn't trigger a build 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-39879) Add pipeline documentation
Title: Message Title Johnny Willemsen closed an issue as Fixed Closing, after installing the plugin there is documentation installed Jenkins / JENKINS-39879 Add pipeline documentation Change By: Johnny Willemsen Status: Open Closed Resolution: Fixed 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/
[JIRA] (JENKINS-39879) Add pipeline documentation
Title: Message Title Johnny Willemsen created an issue Jenkins / JENKINS-39879 Add pipeline documentation Issue Type: Improvement Assignee: wolfs Components: groovy-postbuild-plugin Created: 2016/Nov/19 1:57 PM Priority: Minor Reporter: Johnny Willemsen On https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin there is no documentation how this plugin can be used from a pipeline job. It would help the community if there was some basic documentation with a few examples people can easily copy from Add Comment
[JIRA] (JENKINS-38508) git scm poll doesn't ignore changes with pipeline
Title: Message Title Johnny Willemsen commented on JENKINS-38508 Re: git scm poll doesn't ignore changes with pipeline I also don't 100% understand it. Mostly it seems the polling does work, but in some cases we still see jobs to run even when nothing changed 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-38508) git scm poll doesn't ignore changes with pipeline
Title: Message Title Johnny Willemsen created an issue Jenkins / JENKINS-38508 git scm poll doesn't ignore changes with pipeline Issue Type: Bug Assignee: Unassigned Attachments: config.xml, test.groovy Components: workflow-cps-plugin Created: 2016/Sep/26 2:13 PM Priority: Minor Reporter: Johnny Willemsen We are using the job as attached with the groovy test.groovy file. We poll the SCM for changes but want to ignore any change that is in our jenkins-jobs git repo. This is because in a full setup we poll more repositories which do change. In the jenkins pipeline we use .* as exclude region. This does work unless we clone the same repository in our test.groovy. There we say poll=false, but the repository is polled and at the moment we make a commit to jenkins-jobs.git the job is run. With these configuration we would expect this job to never run, even when we schedule it frequrently Add Comment
[JIRA] (JENKINS-38499) Not possible to trigger from jenkins pipeline
Title: Message Title Johnny Willemsen created an issue Jenkins / JENKINS-38499 Not possible to trigger from jenkins pipeline Issue Type: New Feature Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2016/Sep/26 10:42 AM Priority: Minor Reporter: Johnny Willemsen I would like to use this plugin from a jenkins pipeline to easily trigger a build on the same node, something like step([$class: 'TriggerBuilder', projects: 'windows_reboot', current: true, parameters: 'cleanup_windows_workspace=$WORKSPACE']) Looks this plugin doesn't have support yet to be used from a jenkins pipeline (as far as I could find, no documentation at least) Add Comment
[JIRA] (JENKINS-38486) no node shown when using a pipeline job
Title: Message Title Johnny Willemsen created an issue Jenkins / JENKINS-38486 no node shown when using a pipeline job Issue Type: New Feature Assignee: Unassigned Components: built-on-column-plugin Created: 2016/Sep/25 6:14 PM Priority: Minor Reporter: Johnny Willemsen At the moment the new pipeline based jobs are used the built-on-column plugin doesn't show the node it was last compiled on, just empty text Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38439) CPPScmFlowDefinition with the ability to use the job name in the scm path
Title: Message Title
Johnny Willemsen commented on JENKINS-38439
Re: CPPScmFlowDefinition with the ability to use the job name in the scm path
So in the attached config.xml support for replacing taox11/rhel65_taox11.groovy with taox11/$ {JOB_NAME} .groovy
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-38439) CPPScmFlowDefinition with the ability to use the job name in the scm path
Title: Message Title Johnny Willemsen updated an issue Jenkins / JENKINS-38439 CPPScmFlowDefinition with the ability to use the job name in the scm path Change By: Johnny Willemsen Attachment: config.xml 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-38439) CPPScmFlowDefinition with the ability to use the job name in the scm path
Title: Message Title Johnny Willemsen created an issue Jenkins / JENKINS-38439 CPPScmFlowDefinition with the ability to use the job name in the scm path Issue Type: New Feature Assignee: Unassigned Components: workflow-cps-plugin Created: 2016/Sep/22 8:35 AM Priority: Minor Reporter: Johnny Willemsen Would be useful when the scm path from which the groovy file is loaded could use variables like the job name so that we easily can copy jobs, just give them an unique name and the scm path doesn't need to manually maintained. Made an initial comment on this on JENKINS-28447 Add Comment
[JIRA] (JENKINS-34983) Make text finder plugin compatible with pipeline
Title: Message Title Johnny Willemsen commented on JENKINS-34983 Re: Make text finder plugin compatible with pipeline Made an attempt to add this, haven't done much Jenkins/Java development please review, https://github.com/jenkinsci/text-finder-plugin/pull/6 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-38407) Add support for pipeline plugin
Title: Message Title Johnny Willemsen updated an issue Jenkins / JENKINS-38407 Add support for pipeline plugin Change By: Johnny Willemsen It looks the project-description-setter plugin isn't compatible with the pipeline plugin, tried to add the following to my pipeline writeFile file: 'project_description.txt', text: ''' testing'''} step([$class: 'project-description-setter ', filename: 'project_description.txt'])This results injava.lang.UnsupportedOperationException: no known implementation of interface jenkins.tasks.SimpleBuildStep is named project-description-setterWould be nice if we could also do the following so that we don't need a filename step([$class: 'project-description-setter ', text: 'foo']) See https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md 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 em
[JIRA] (JENKINS-38407) Add support for pipeline plugin
Title: Message Title Johnny Willemsen created an issue Jenkins / JENKINS-38407 Add support for pipeline plugin Issue Type: Bug Assignee: bap Components: project-description-setter-plugin Created: 2016/Sep/21 10:04 AM Environment: Jenkins 2.7.4 Priority: Minor Reporter: Johnny Willemsen It looks the project-description-setter plugin isn't compatible with the pipeline plugin, tried to add the following to my pipeline writeFile file: 'project_description.txt', text: ''' testing '''} step([$class: 'project-description-setter ', filename: 'project_description.txt']) This results in java.lang.UnsupportedOperationException: no known implementation of interface jenkins.tasks.SimpleBuildStep is named project-description-setter Would be nice if we could also do the following so that we don't need a filename step([$class: 'project-description-setter ', text: 'foo']) Add Comment
[JIRA] (JENKINS-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title Johnny Willemsen commented on JENKINS-36322 Re: NaN execution time may appear if a stage gets terminated incorrectly Added a screen dump with similar output but "NaNy NaNd" 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-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title Johnny Willemsen updated an issue Jenkins / JENKINS-36322 NaN execution time may appear if a stage gets terminated incorrectly Change By: Johnny Willemsen Attachment: fp5mti.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-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Johnny Willemsen commented on JENKINS-28447 Re: CpsScmFlowDefinition does not resolve variables Would be useful for our use case when the Script Path could use the job name, that way we can have a generic setup where we just have to copy jobs and rename them, the script path will use the correct file for that job from scm 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-35026) Pipeline script from SCM triggers builds on sub pipeline change
Title: Message Title Johnny Willemsen updated an issue Jenkins / JENKINS-35026 Pipeline script from SCM triggers builds on sub pipeline change Change By: Johnny Willemsen Attachment: poll.txt 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-35026) Pipeline script from SCM triggers builds on sub pipeline change
Title: Message Title Johnny Willemsen commented on JENKINS-35026 Re: Pipeline script from SCM triggers builds on sub pipeline change I am attaching a text file with jenkins job that pulls the pipeline script from scm, job is triggered on a schedule but the repo we get the script from isn't pulled the contents of the script, have to us two repositories to get the same, the jenkins-jobs git repo is the same as we get the script from the result of a poll, we had a chagne in jenkins-jobs, but that shouldn't trigger a build 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-35026) Pipeline script from SCM triggers builds on sub pipeline change
Title: Message Title
Johnny Willemsen edited a comment on JENKINS-35026
Re: Pipeline script from SCM triggers builds on sub pipeline change
I see something similar in our setup, we checkout the pipeline from SCM (for example http://our-git-url/git/jenkins-pipelines.git) but exclude .* from the polling because we dont' want all our builds to retrigger at the moment something in that git repository changs. In the pipeline script we use a stage as below, but at the moment the jenkins job is triggered through a timed SCM pull it does rebuild at the moment jenkins-pipelines.git has a change, even that we have said poll to false {{ stage('Buildtools checkout') {dir ('buildtools') { git changelog: false, poll: false, url: 'http://our-git-url/git/jenkins-pipelines.git'}dir ('jenkins-jobs') { git changelog: false, poll: false, url: 'http://our-git-url/git/another-repo.git'} } }}
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-35026) Pipeline script from SCM triggers builds on sub pipeline change
Title: Message Title
Johnny Willemsen commented on JENKINS-35026
Re: Pipeline script from SCM triggers builds on sub pipeline change
I see something similar in our setup, we checkout the pipeline from SCM (for example http://our-git-url/git/jenkins-pipelines.git) but exclude .* from the polling because we dont' want all our builds to retrigger at the moment something in that git repository changs. In the pipeline script we use a stage as below, but at the moment the jenkins job is triggered through a timed SCM pull it does rebuild at the moment jenkins-pipelines.git has a change, even that we have said poll to false {{ stage('Buildtools checkout') { dir ('buildtools') { git changelog: false, poll: false, url: 'http://our-git-url/git/jenkins-pipelines.git' } dir ('jenkins-jobs') { git changelog: false, poll: false, url: 'http://our-git-url/git/another-repo.git' } }}}
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] [git-client-plugin] (JENKINS-33130) Add feature to not do any clone as part of the advanced clone behaviours
Title: Message Title Johnny Willemsen created an issue Jenkins / JENKINS-33130 Add feature to not do any clone as part of the advanced clone behaviours Issue Type: Improvement Assignee: Nicolas De Loof Components: git-client-plugin Created: 24/Feb/16 2:25 PM Environment: linux Priority: Minor Reporter: Johnny Willemsen We are using the git-client poll support to see if there are any changes in a set of git repositories (using through the multiple-scms-plugin). Currently we can configure a shallow clone as part of the advanced clone behaviours, but it would be nice if we can configure no clone at all. Only use the git client poll support without that the client does a clone of any code. Getting the real code from git is done later by some additional scripting which does use a special directory structure based on other settings
[JIRA] [git-plugin] (JENKINS-33124) git ls-mote could be more optimal when we select a specif branch
Title: Message Title Johnny Willemsen created an issue Jenkins / JENKINS-33124 git ls-mote could be more optimal when we select a specif branch Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 24/Feb/16 11:51 AM Environment: Linux Priority: Minor Reporter: Johnny Willemsen We are using git polling with a specific branch, for example we configure git://git.foo.nl/atcd.git as repository URL and refs/heads/master as branch to build. For the polling we see that the following command is used: git -c core.askpass=true ls-remote -h git://git.foo.nl/atcd.git Which returns all heads, it would be more optimal when the following is used, that only returns 1 branch git -c core.askpass=true ls-remote -h git://git.foo.nl/atcd.git refs/heads/master
[JIRA] [multiple-scms-plugin] (JENKINS-25253) When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Title: Message Title Johnny Willemsen commented on JENKINS-25253 Re: When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build. Tested now my proposed addition, had to make a small change in another place, see https://github.com/jenkinsci/multiple-scms-plugin/pull/18 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [multiple-scms-plugin] (JENKINS-25253) When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Title: Message Title
Johnny Willemsen updated an issue
Jenkins / JENKINS-25253
When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Change By:
Johnny Willemsen
Comment:
Note, I am not a Java person and the code below is not tested at all, but could this be of help, just based on the documentation above. If this is useful, let me know, can create a pull request when that would help. Addition to MultipleSCM.java// Only return supportsPolling when all scms do report back that// they supports polling@Overridepublic boolean supportsPolling(){ for(SCM scm : scms) {if (!scm.supportsPolling()) return false; } return true;}// When one scm does require a workspace we return true, else// we don't need a workspace for polling@Overridepublic boolean requiresWorkspaceForPolling(){ for(SCM scm : scms) {if (scm.requiresWorkspaceForPolling()) return true; } return false;}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [multiple-scms-plugin] (JENKINS-25253) When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Title: Message Title
Johnny Willemsen edited a comment on JENKINS-25253
Re: When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Note, I am not a Java person and the code below is not tested at all, but could this be of help, just based on the documentation above. If this is useful, let me know, can create a pull request when that would help. Addition to MultipleSCM.java// Only return supportsPolling when all scms do report back that// they supports polling@Overridepublic boolean supportsPolling(){ for(SCM scm : scms) {if ( ! scm.supportsPolling() == false ) return false; } return true;}// When one scm does require a workspace we return true, else// we don't need a workspace for polling@Overridepublic boolean requiresWorkspaceForPolling(){ for(SCM scm : scms) {if (scm.requiresWorkspaceForPolling() == true ) return true; } return false;}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [multiple-scms-plugin] (JENKINS-25253) When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Title: Message Title
Johnny Willemsen edited a comment on JENKINS-25253
Re: When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Note, I am not a Java person and the code below is not tested at all, but could this be of help, just based on the documentation above. If this is useful, let me know, can create a pull request when that would help. Addition to MultipleSCM.java {{ // Only return supportsPolling when all scms do report back that// they supports polling@Overridepublic boolean supportsPolling(){ for(SCM scm : scms) {if (scm.supportsPolling() == false) return false; } return true;}// When one scm does require a workspace we return true, else// we don't need a workspace for polling@Overridepublic boolean requiresWorkspaceForPolling(){ for(SCM scm : scms) {if (scm.requiresWorkspaceForPolling() == true) return true; } return false;} }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [multiple-scms-plugin] (JENKINS-25253) When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Title: Message Title
Johnny Willemsen edited a comment on JENKINS-25253
Re: When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Note, I am not a Java person and the code below is not tested at all, but could this be of help, just based on the documentation above. If this is useful, let me know, can create a pull request when that would help. Addition to MultipleSCM.java {{ // Only return supportsPolling when all scms do report back that// they supports polling@Overridepublic boolean supportsPolling(){ for(SCM scm : scms) {if (scm.supportsPolling() == false) return false; } return true;}// When one scm does require a workspace we return true, else// we don't need a workspace for polling@Overridepublic boolean requiresWorkspaceForPolling(){ for(SCM scm : scms) {if (scm.requiresWorkspaceForPolling() == true) return true; } return false;} }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [multiple-scms-plugin] (JENKINS-25253) When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Title: Message Title
Johnny Willemsen commented on JENKINS-25253
Re: When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Note, I am not a Java person and the code below is not tested at all, but could this be of help, just based on the documentation above. If this is useful, let me know, can create a pull request when that would help. Addition to MultipleSCM.java
// Only return supportsPolling when all scms do report back that // they supports polling @Override public boolean supportsPolling() { for(SCM scm : scms) { if (scm.supportsPolling() == false) return false; }
return true; }
// When one scm does require a workspace we return true, else // we don't need a workspace for polling @Override public boolean requiresWorkspaceForPolling() { for(SCM scm : scms) { if (scm.requiresWorkspaceForPolling() == true) return true; }
return false; }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [multiple-scms-plugin] (JENKINS-25253) When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build.
Title: Message Title Johnny Willemsen commented on JENKINS-25253 Re: When MultiSCM is used to poll git, it will always rebuild if the workspace is cleaned post build. Could this be because this plugin doesn't implement requiresWorkspaceForPolling (see http://javadoc.jenkins-ci.org/hudson/scm/SCM.html#requiresWorkspaceForPolling%28%29). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-28151) if node switched off after execution some garbage generated
Title: Message Title Johnny Willemsen commented on JENKINS-28151 Re: if node switched off after execution some garbage generated We see a similar issue on Windows, the directory is renamed because of the asynchronoous delete, but we reboot the node in the next jenkins step and the asynchronous delete then isn't finished. Also because of the size of our workspace we see that the asynchronous delete together with the fresh checked out tree is causing our systems to run out of diskspace. Would be helpful for us to have an option to disable the asynchronous delete, we know our build takes more, but it saves us ton of diskspace. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ssh-slaves] (JENKINS-18706) ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel
Johnny Willemsen edited a comment on JENKINS-18706 ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel We see here similar problems, time of the slaves is out of sync according to Jenkins with 5 months, but that is not the case. With Solaris 10 x86_64 and Sparc slaves we also have problems connecting using the same error, Solaris 10 ships with "java full version "1.5.0_12-b04". The log when I am using Java webstart: Jul 24, 2013 1:15:46 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http://jenkins.remedy.nl/] Jul 24, 2013 1:15:46 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins.remedy.nl:45673 Jul 24, 2013 1:15:46 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Jul 24, 2013 1:15:46 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected Jul 24, 2013 1:15:47 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel channel java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2498) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1273) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Jul 24, 2013 1:15:47 PM hudson.remoting.jnlp.Main$CuiListener status This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-18706) ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel
Johnny Willemsen commented on JENKINS-18706 ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel We see here similar problems, time of the slaves is out of sync according to Jenkins with 5 months, but that is not the case. With Solaris 10 x86_64 and Sparc slaves we also have problems connecting using the same error, Solaris 10 ships with "java full version "1.5.0_12-b04" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
