[JIRA] (JENKINS-60773) Milestone aborting old builds before passing next milestone
Title: Message Title Taylor Patton updated an issue Jenkins / JENKINS-60773 Milestone aborting old builds before passing next milestone Change By: Taylor Patton Environment: Jenkins 2.204.1Milestone Step Plugin 1.3.1Input Step Plugin 2.11 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204034.157903700.8347.1579039380069%40Atlassian.JIRA.
[JIRA] (JENKINS-60773) Milestone aborting old builds before passing next milestone
Title: Message Title Taylor Patton updated an issue Jenkins / JENKINS-60773 Milestone aborting old builds before passing next milestone Change By: Taylor Patton Component/s: pipeline-input-step-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204034.157903700.8346.1579039260139%40Atlassian.JIRA.
[JIRA] (JENKINS-60773) Milestone aborting old builds before passing next milestone
Title: Message Title Taylor Patton updated an issue Jenkins / JENKINS-60773 Milestone aborting old builds before passing next milestone Change By: Taylor Patton Component/s: pipeline-milestone-step-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204034.157903700.8345.1579037760068%40Atlassian.JIRA.
[JIRA] (JENKINS-60773) Milestone aborting old builds before passing next milestone
Title: Message Title Taylor Patton updated an issue Jenkins / JENKINS-60773 Milestone aborting old builds before passing next milestone Change By: Taylor Patton Summary: Milestone cancelling aborting old builds before passing next milestone Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204034.157903700.8344.1579037460079%40Atlassian.JIRA.
[JIRA] (JENKINS-60773) Milestone cancelling old builds before passing next milestone
Title: Message Title
Taylor Patton created an issue
Jenkins / JENKINS-60773
Milestone cancelling old builds before passing next milestone
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-01-14 21:23
Priority:
Minor
Reporter:
Taylor Patton
I may be misunderstanding how to use the milestone, sorry in advance if I am. I have a simple pipeline configured as follows:
node('some-node') {
stage('First') {
milestone 1
input(id: 'input', message: 'Deploy?')
}
stage('Second') {
milestone 2
}
}
If I have builds 1 and 2 sitting at the input step, and I "reject" build #2 so that it does not proceed any further, build #1 is still automatically aborted. This does not make sense to me, because build #2 has not reached "milestone 2". Please advise.
Add Comment
[JIRA] (JENKINS-56112) copyRemoteArtifact flattens directory if only 1 file chosen to copy
Title: Message Title Taylor Patton updated an issue Jenkins / JENKINS-56112 copyRemoteArtifact flattens directory if only 1 file chosen to copy Change By: Taylor Patton Summary: copyRemoteArtifact flattens directory if selector is SpecificRemoteBuildSelector only 1 file chosen to copy 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-56112) copyRemoteArtifact flattens directory if selector is SpecificRemoteBuildSelector
Title: Message Title
Taylor Patton updated an issue
Jenkins / JENKINS-56112
copyRemoteArtifact flattens directory if selector is SpecificRemoteBuildSelector
Change By:
Taylor Patton
The following command works fine, without flattening directory of copied artifacts:{code:java}copyRemoteArtifacts from: 'jenkins:///test-job', includes: 'folder/file.txt ,folder/file2.txt '{code}The remote file is files are copied as 'folder/file.txt' and 'folder/file2.txt' as expected.However, if you use the "SpecificRemoteBuildSelector" I just copy 1 file as such:{code:java} copyRemoteArtifacts from: 'jenkins:///test-job', includes: 'folder/file.txt' , selector: [$class: 'SpecificRemoteBuildSelector', number: '1'] {code}The copied file does not have the directory anymore, and is copied as 'file.txt' instead of 'folder/file.txt'.
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-56112) copyRemoteArtifact flattens directory if selector is SpecificRemoteBuildSelector
Title: Message Title Taylor Patton created an issue Jenkins / JENKINS-56112 copyRemoteArtifact flattens directory if selector is SpecificRemoteBuildSelector Issue Type: Bug Assignee: Unassigned Components: cloudbees-enterprise-plugins Created: 2019-02-12 21:56 Environment: CloudBees Jenkins Enterprise 2.73.32.0.1-fixed Operations Center Plugin 2.73.0.2 Priority: Major Reporter: Taylor Patton The following command works fine, without flattening directory of copied artifacts: copyRemoteArtifacts from: 'jenkins:///test-job', includes: 'folder/file.txt' The remote file is copied as 'folder/file.txt' as expected. However, if you use the "SpecificRemoteBuildSelector" as such: copyRemoteArtifacts from: 'jenkins:///test-job', includes: 'folder/file.txt', selector: [$class: 'SpecificRemoteBuildSelector', number: '1'] The copied file does not have the directory anymore, and is copied as 'file.txt' instead of 'folder/file.txt'.
[JIRA] (JENKINS-44609) Docker inspect failing on named multi-stage builds
Title: Message Title
Taylor Patton edited a comment on JENKINS-44609
Re: Docker inspect failing on named multi-stage builds
Also seeing this same issue, but interestingly enough, it works in 1 job but not another, doing almost the exact same thing.Working code in question:{code:java} withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) { docker.build('mydockerimage', "--file ${DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${BUILD_NUMBER} .") } {code}Code that doesn't work:{code:java} withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) { docker.build('mydockerimage', "--file ${myProperties.DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${params.BUILD_TO_DEPLOY} .") } {code}Where "myProperties" is read from a properties file using "readProperties" from stage utils plugin. The docker image seems to be built fine in both cases, but in the latter, we see the error:{code:java}Successfully built 204ce2321dabSuccessfully tagged [Pipeline] dockerFingerprintFrom[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[Pipeline] // withDockerRegistry[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Cannot retrieve .Id from 'docker inspect'{code}We do use the multi-stage docker build with "AS name" for the docker stages in the starting Dockerfile being built.
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-44609) Docker inspect failing on named multi-stage builds
Title: Message Title
Taylor Patton edited a comment on JENKINS-44609
Re: Docker inspect failing on named multi-stage builds
Also seeing this same issue, but interestingly enough, it works in 1 job but not another, doing almost the exact same thing.Working code in question:{code:java}withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) {docker.build('mydockerimage', "--file ${DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${BUILD_NUMBER} .")} {code}Code that doesn't work:{code:java}withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) {docker.build('mydockerimage', "--file ${myProperties.DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${ BUILD_NUMBER params.BUILD_TO_DEPLOY } .")} {code}Where "myProperties" is read from a properties file using "readProperties" from stage utils plugin. The docker image seems to be built fine in both cases, but in the latter, we see the error:{code:java}Successfully built 204ce2321dabSuccessfully tagged [Pipeline] dockerFingerprintFrom[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[Pipeline] // withDockerRegistry[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: Cannot retrieve .Id from 'docker inspect'{code}We do use the multi-stage docker build with "AS name" for the docker stages in the starting Dockerfile being built.
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-44609) Docker inspect failing on named multi-stage builds
Title: Message Title
Taylor Patton commented on JENKINS-44609
Re: Docker inspect failing on named multi-stage builds
Also seeing this same issue, but interestingly enough, it works in 1 job but not another, doing almost the exact same thing. Working code in question:
withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) {
docker.build('mydockerimage', "--file ${DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${BUILD_NUMBER} .")
}
Code that doesn't work:
withCredentials([string(credentialsId: 'secret-key', variable: 'secret')]) {
docker.build('mydockerimage', "--file ${myProperties.DOCKERFILE} --pull --build-arg KEY=${secret} --build-arg BUILD_NUMBER=${BUILD_NUMBER} .")
}
Where "myProperties" is read from a properties file using "readProperties" from stage utils plugin. The docker image seems to be built fine in both cases, but in the latter, we see the error:
Successfully built 204ce2321dab
Successfully tagged
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[Pipeline] // withDockerRegistry
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.io.IOException: Cannot retrieve .Id from 'docker inspect'
We do use the multi-stage docker build with "AS name" for the docker stages in the starting Dockerfile being built.
Add Comment
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Taylor Patton commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should This critical issue is maddening. It's almost as if we have to separate our pipeline into small components (jobs) like we did with freestyle jobs, for the build status reporting to make sense. 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-50557) GCR Credentials Plugin does not work
Title: Message Title Taylor Patton updated an issue Jenkins / JENKINS-50557 GCR Credentials Plugin does not work Change By: Taylor Patton Comment: Are you sure you have both "Google OAuth Credentials plugin" and "Google Container Registry Auth Plugin" installed? Also make sure that your actual jenkins credential ID is not prepended with "gcr:". Those were my 2 mistakes Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-38046) Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Title: Message Title Taylor Patton commented on JENKINS-38046 Re: Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline Will this capability be added to gerrit-trigger-plugin? I am weary of installing another gerrit plugin and having 2 ways of configuring pipelines (multi-branch and regular). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50557) GCR Credentials Plugin does not work
Title: Message Title Taylor Patton commented on JENKINS-50557 Re: GCR Credentials Plugin does not work Are you sure you have both "Google OAuth Credentials plugin" and "Google Container Registry Auth Plugin" installed? Also make sure that your actual jenkins credential ID is not prepended with "gcr:". Those were my 2 mistakes Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-29581) Error when binding credentials to a job
Title: Message Title
Taylor Patton reopened an issue
This same thing is happening to me with: Credentials Binding Plugin 1.8 Credentials Plugin 2.1.4 Jenkins 1.625.3 This happens whenever I choose a credential to use as an env variable (both conjoined and separated). The issue is resolved by downgrading Credentials Plugin to 1.18
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper from {"bindings":{"usernameVariable":"machine_user","passwordVariable":"machine_pw","credentialsId":["60005674-a10b-413e-b2b5-e217dd960c21",""],"stapler-class":"org.jenkinsci.plugins.credentialsbinding.impl.UsernamePasswordMultiBinding","$class":"org.jenkinsci.plugins.credentialsbinding.impl.UsernamePasswordMultiBinding"}} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at
[JIRA] [docker-commons-plugin] (JENKINS-32792) Unable to push Docker images due to failing image ID length check
Title: Message Title Taylor Patton commented on JENKINS-32792 Re: Unable to push Docker images due to failing image ID length check Can bypass the failure if I uncheck "Create fingerprints" in Docker Build Advanced section 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.
