[JIRA] (JENKINS-35173) jobs not removed when branch gets removed
Title: Message Title Dominik Bartholdi commented on JENKINS-35173 Re: jobs not removed when branch gets removed the root cause of this is most probably not in jenkins, but in a bug in bitbucket see JENKINS-38256 and https://bitbucket.org/site/master/issues/13524 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-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title Tom FENNELLY commented on JENKINS-39661 Re: Investigate performance of Pipeline /activity and /runs REST endpoint James Dumay Assigned to me now. Thanks. 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-38711) slave.jar should install UncaughtExceptionHandler
Title: Message Title Oleg Nenashev commented on JENKINS-38711 Re: slave.jar should install UncaughtExceptionHandler Took the issue to the remoting EPIC. It's not exactly remoting, but it makes sense to do it as a part of the stability stories 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-38134) Generate checksums for war, Windows and OS X distributables
Title: Message Title Armando Fernandez resolved as Fixed Jenkins / JENKINS-38134 Generate checksums for war, Windows and OS X distributables Change By: Armando Fernandez Status: In Progress Resolved 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/d/optout.
[JIRA] (JENKINS-38134) Generate checksums for war, Windows and OS X distributables
Title: Message Title Armando Fernandez commented on JENKINS-38134 Re: Generate checksums for war, Windows and OS X distributables Shasums are now being generated for osx, windows and war distributables. Examples: OSS OsX distributable. See how latest releases have their sha256 files available. OSS Windows distributable. See how latest releases have their sha256 files available. OSS War (2.30). See how 2.30, latest war version, has its sha256 file available. Marking this issue as resolved now. 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-39571) Jenkins doesn't start after plugin update
Title: Message Title M U reopened an issue Jenkins / JENKINS-39571 Jenkins doesn't start after plugin update Change By: M U Resolution: Incomplete Status: Resolved Reopened 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-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title Ioannis Canellos commented on JENKINS-39664 Re: Docker builds do not work with Kubernetes Pipeline plugin We need more details in order to identify the problem and help. If I understand correctly the script you pasted is something that works. Can you please paste that fails? Also can you please provide the full stack trace. 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-25146) When the anonymous user has no access rights, userContent is inaccessible
Title: Message Title Michael Szekeres commented on JENKINS-25146 Re: When the anonymous user has no access rights, userContent is inaccessible If the /userContent directory is used for custom css files and custom Images (as suggested in some threads) access control is not needed. I think a option to Switch access control on/off - or a second folder without access control would be useful in many cases. 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-39666) xcode plugin hangs when using workspace
Title: Message Title Maiko Hermans created an issue Jenkins / JENKINS-39666 xcode plugin hangs when using workspace Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 2016/Nov/11 8:40 AM Environment: jenkins 2.19.2, xcode 8 Labels: xcode Priority: Blocker Reporter: Maiko Hermans I'm trying to run tests from a project that uses cocoapods. This means I have to specify the workspace name. When I do so as well as giving the scheme name the xcode plugin will just hang at this point forever (I actually let it run for 30min before killing it several times) Going to invoke xcodebuild:, scheme: ttt, sdk: DEFAULT, workspace: ttt, configuration: Debug, clean: NO, archive:NO, symRoot: DEFAULT, configurationBuildDir: DEFAULT, codeSignIdentity: DEFAULT [lbp-iOS] $ /usr/bin/xcodebuild -scheme ttt -workspace ttt.xcworkspace -configuration Debug build test -destination "platform=iOS Simulator,name=iPhone 6,OS=10.1" It seems to me that there might be something wrong with the plugin that causes it to hang in this specific case. I've also created a stackoverflow for this http://stackoverflow.com/questions/40536087/unit-test-ios-with-jenkins.
[JIRA] (JENKINS-38822) Service fails to restart when both .jpi and .hpi files found
Title: Message Title Oleg Nenashev commented on JENKINS-38822 Re: Service fails to restart when both .jpi and .hpi files found I agree it would be useful to fix it (e.g. by giving a priority to JPI files), but it's rather an improvement, not a bug 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-38822) Service fails to restart when both .jpi and .hpi files found
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38822 Service fails to restart when both .jpi and .hpi files found Change By: Oleg Nenashev Issue Type: Bug Improvement 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-38721) Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38721 Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy Change By: Oleg Nenashev Component/s: pipeline 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-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title Tom FENNELLY assigned an issue to Tom FENNELLY Jenkins / JENKINS-39661 Investigate performance of Pipeline /activity and /runs REST endpoint Change By: Tom FENNELLY Assignee: Tom FENNELLY 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-39534) When Jenkins restarts, the groovy scripts are lost
Title: Message Title Bruno P. Kinoshita resolved as Fixed Hopefully fixed in 1.5.1. Version 1.5.0 was removed from the update center. You can read more about the issue in this blog post. Jenkins / JENKINS-39534 When Jenkins restarts, the groovy scripts are lost Change By: Bruno P. Kinoshita Status: Open Resolved 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
[JIRA] (JENKINS-39534) When Jenkins restarts, the groovy scripts are lost
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Jenkins / JENKINS-39534 When Jenkins restarts, the groovy scripts are lost Change By: Bruno P. Kinoshita Status: Resolved Closed 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-38408) NullPointerException on running any gcloud command with oauth credentials
Title: Message Title Oleg Nenashev assigned an issue to João Luís Jenkins / JENKINS-38408 NullPointerException on running any gcloud command with oauth credentials Change By: Oleg Nenashev Assignee: João Luís 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-38408) NullPointerException on running any gcloud command with oauth credentials
Title: Message Title Oleg Nenashev commented on JENKINS-38408 Re: NullPointerException on running any gcloud command with oauth credentials Not a core bug 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-38408) NullPointerException on running any gcloud command with oauth credentials
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38408 NullPointerException on running any gcloud command with oauth credentials Change By: Oleg Nenashev Component/s: gcloud-sdk-plugin Component/s: core 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-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title Carlos Sanchez commented on JENKINS-35246 Re: Kubernetes nodes not getting deleted when a pipeline job fails Are you saying that the Pods don't get deleted in kubernetes, the jenkins slave is not deleted in Jenkins, or both ? 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-39656) [Questrion] Version Information
Title: Message Title Stephen Connolly commented on JENKINS-39656 Re: [Questrion] Version Information No clue about versioneye... never heard of it... seems buggy in the extreme if it is failing for any specific case. The Jenkins update center filters the responses of plugin updates depending on the version of Jenkins that you are running. Basically the backend for the jenkins update center will limit the versions of plugins that it advertises to those plugins that are compatible with specific baseline versions of Jenkins. Thus: https://updates.jenkins-ci.org/1.580/update-center.json will have the newest version of credentials that is compatible with 1.580+... which is 1.28 whereas https://updates.jenkins-ci.org/1.609/update-center.json has the newest version compatible with 1.609+... which is 2.1.8 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-39637) How to remove jsessionid on the url when logging in
Title: Message Title Oleg Nenashev commented on JENKINS-39637 Re: How to remove jsessionid on the url when logging in I suppose we will have to upgrade or to build your custom Jenkins core with a patch. Currently we do not provide patches for Jenkins 1.x, but the upgrade is mostly safe 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-39009) User#isIdOrFullnameAllowed() should disallow system names with special symbols
Title: Message Title Oleg Nenashev commented on JENKINS-39009 Re: User#isIdOrFullnameAllowed() should disallow system names with special symbols CC James Nord who requested it 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-38822) Jenkins startup should handle the case when both .jpi and .hpi plugin files are found
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38822 Jenkins startup should handle the case when both .jpi and .hpi plugin files are found Change By: Oleg Nenashev Summary: Service fails to restart Jenkins startup should handle the case when both .jpi and .hpi plugin files are found 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-38721) Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy
Title: Message Title Oleg Nenashev commented on JENKINS-38721 Re: Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy It is a regression due to JENKINS-36594. https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/model/CauseOfInterruption/UserInterruption/summary.groovy needs to be 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/d/optout.
[JIRA] (JENKINS-38721) Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38721 Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy Change By: Oleg Nenashev Labels: exception jelly pipeline regression 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-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title Tom FENNELLY started work on JENKINS-39661 Change By: Tom FENNELLY Status: Open In Progress 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-38711) slave.jar should install UncaughtExceptionHandler
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-38711 slave.jar should install UncaughtExceptionHandler Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-39645) Migrate to 2.17 parent POM
Title: Message Title Evaristo Gutierrez updated JENKINS-39645 Jenkins / JENKINS-39645 Migrate to 2.17 parent POM Change By: Evaristo Gutierrez Status: In Progress Review 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-39665) Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin
Title: Message Title Java Dev created an issue Jenkins / JENKINS-39665 Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin Issue Type: Improvement Assignee: Unassigned Attachments: uno-choice-plugin.png Components: active-choices-plugin Created: 2016/Nov/11 8:37 AM Environment: - Operating System: Ubuntu Server 14.04 LTS 64Bit - Jenkins Version: 2.20 - Java(TM) SE Runtime Environment: (build 1.8.0_101-b13) - Not run in a container. - Debian install - Firefox 49.0.2 - Chrome Version 54.0.2840.71 (64-bit) Labels: scrollbar _javascript_ jenkins plugin Priority: Minor Reporter: Java Dev Adding an Active Choices Reactive Parameter with choice type of radio buttons or check boxes produces unnecessary scrollbars on the [build with parameters] screen (see attached image). Jenkins url is: https:// [ci_url] /job/ [job_name] /build?delay=0sec Height calculation in the _javascript_ function of checkboxContent.jelly and radioContent.jelly seems to create a height value which is too small. I have created a push request on GitHub with my own solution, should you choose to accept it.
[JIRA] (JENKINS-38721) Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-38721 Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters
Title: Message Title Bruno P. Kinoshita closed an issue as Fixed Jenkins / JENKINS-39620 Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters Change By: Bruno P. Kinoshita Status: Resolved Closed 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-39534) When Jenkins restarts, the groovy scripts are lost
Title: Message Title Bruno P. Kinoshita updated JENKINS-39534 Jenkins / JENKINS-39534 When Jenkins restarts, the groovy scripts are lost Change By: Bruno P. Kinoshita Status: Reopened Open 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-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters
Title: Message Title Bruno P. Kinoshita resolved as Fixed Should be fixed in 1.5.1, released moments ago. 1.5.0 was removed. Blog about that here: http://biouno.org/2016/11/11/what-happens-when-you-make-a-java-member-variable-transient-in-a-jenkins-plugin Jenkins / JENKINS-39620 Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters Change By: Bruno P. Kinoshita Status: Open Resolved 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
[JIRA] (JENKINS-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title
Markus May edited a comment on JENKINS-39664
Re: Docker builds do not work with Kubernetes Pipeline plugin
Sure, the folllowing script does give the following "output": {code:groovy} [Pipeline] podTemplate[Pipeline] {[Pipeline] nodeRunning on kubernetes-1d1bed95d3ea4665b3bf13e07380c7b0-12552de6d1a in /home/jenkins/workspace/docker-mysql[Pipeline] {[Pipeline] stage[Pipeline] { (Preparation)[Pipeline] gitCloning the remote Git repositoryCloning repository https://github.com/devopskube/docker-mysql.git > git init /home/jenkins/workspace/docker-mysql # timeout=10Fetching upstream changes from https://github.com/devopskube/docker-mysql.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/devopskube/docker-mysql.git + refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/devopskube/ docker -mysql.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/devopskube/docker-mysql.git # timeout=10Fetching upstream changes from https://github.com/devopskube/docker-mysql.git > git fetch --tags --progress https://github.com/devopskube/docker-mysql.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision 73d040979d4faeb597ddcc8d80198eb0bdddfd2c (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 73d040979d4faeb597ddcc8d80198eb0bdddfd2c > git branch -a -v --no-abbrev # timeout=10 > git checkout -b master 73d040979d4faeb597ddcc8d80198eb0bdddfd2c > git rev-list 73d040979d4faeb597ddcc8d80198eb0bdddfd2c # timeout=10[Pipeline] container[Pipeline] {[Pipeline] stage[Pipeline] { (Build the docker image)[Pipeline] sh[docker-mysql] Running shell scriptExecuting shell script inside container [docker] of pod [kubernetes-1d1bed95d3ea4665b3bf13e07380c7b0-12552de6d1a]Executing command: sh -c echo $$ > '/home/jenkins/workspace/docker-mysql@tmp/durable-1dc92f56/pid'; jsc=durable-27d97ad1c907eb144d854b5bac745183; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/docker-mysql@tmp/durable-1dc92f56/script.sh' > '/home/jenkins/workspace/docker-mysql@tmp/durable-1dc92f56/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/docker-mysql@tmp/durable-1dc92f56/jenkins-result.txt' /home/jenkins # [6ncd /home/jenkins/workspace/docker-mysql/home/jenkins/workspace/docker-mysql # sh -c echo $$ > '/home/jenkins/workspace/docker-mysql@tmp/durable-1dc92f56/pid'; jsc=durable-27d97ad1c907eb144d854b5bac745183; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/docker-mysql@tmp/durable-1dc92f56/script.sh' > '/home/jenkins/workspace/docker-mysql@tmp/durable-1dc92f56/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/docker-mysql@tmp/durable-1dc92f56/jenkins-result.txt' + docker build -t devopskube/mysql .Sending build context to Docker daemon 13.31 kB/home/jenkins/workspace/docker-mysql # exit Here the build of the docker image happens... Successfully built 8c3d46bc959b[Pipeline] dockerFingerprintFromExecuting shell script inside container [docker] of pod [kubernetes-1d1bed95d3ea4665b3bf13e07380c7b0-12552de6d1a]Executing command: docker inspect -f {{.Id}} devopskube/mysql [Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] End of Pipelinejava.io.IOException: Cannot retrieve .Id from 'docker inspectdevopskube/mysql' at
[JIRA] (JENKINS-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title
Ioannis Canellos commented on JENKINS-39664
Re: Docker builds do not work with Kubernetes Pipeline plugin
I tried the script locally and I noticed a couple of things:
node doesn't specify a label. Might not be a problem, but you'd better refer to the podTemplate's label: node('docker-mysql').
container('docker') should be container(name: 'docker'). In my env this gives an error.
I had to change the version of the docker image, to align with my docker server.
If none of these, help I would check the version of the docker workflow plugin.
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-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title Ioannis Canellos commented on JENKINS-39664 Re: Docker builds do not work with Kubernetes Pipeline plugin Sorry, I was wrong. In my environment the image is built, but I do get a similar error, in the end. It seems that this is more of a docker workflow issue, so I can't do much here. 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-38807) Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection
Title: Message Title Oleg Nenashev commented on JENKINS-38807 Re: Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection It does. Jenkins has a complex process termination logic (ProcessKiller, ProcessKillingVeto extension points), which require a connection to master in order to be invoked properly. From a user perspective I agree it's a serious UX bug 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-38807) Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38807 Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection Change By: Oleg Nenashev Labels: regression ux 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-38807) Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection
Title: Message Title Oleg Nenashev commented on JENKINS-38807 Re: Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection Not a regression 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-38807) Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38807 Jenkins 2.7.4 seems to leave behind Java processes (on Windows slave) if the build is aborted/slave loses connection Change By: Oleg Nenashev Labels: regression ux 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-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title
Markus May commented on JENKINS-39664
Re: Docker builds do not work with Kubernetes Pipeline plugin
Sure, the folllowing script does give the following "output":
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
+ docker build -t devopskube/mysql .
Sending build context to Docker daemon 13.31 kB
/home/jenkins/workspace/docker-mysql # exit
Here the build of the docker image happens...
Successfully built 8c3d46bc959b
[Pipeline] dockerFingerprintFrom
Executing shell script inside container [docker] of pod [kubernetes-1d1bed95d3ea4665b3bf13e07380c7b0-12552de6d1a]
Executing command: docker inspect -f {{.Id}} devopskube/mysql
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // container
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // podTemplate
[Pipeline] End of Pipeline
java.io.IOException: Cannot retrieve .Id from 'docker inspectdevopskube/mysql'
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:190)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:115)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:75)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52)
at hudson.security.ACL.impersonate(ACL.java:221)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Finished: FAILURE
The script is just slightly adopted:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
podTemplate(label: 'docker-mysql', containers: [
containerTemplate(name: 'docker', image: 'docker:1.12.3-dind', ttyEnabled: true, command: 'cat', privileged: true, instanceCap: 1),
containerTemplate(name: 'jnlp', image: 'jenkinsci/jnlp-slave:2.62-alpine', args: '${computer.jnlpmac} ${computer.name}'),
],
volumes: [
hostPathVolume(mountPath: "/var/run/docker.sock", hostPath: "/var/run/docker.sock")
]) {
node() {
stage('Preparation') { // for display purposes
git url: 'https://github.com/devopskube/docker-mysql.git'
[JIRA] (JENKINS-17277) Jenkins iOS job broken because “FATAL: Log statements out of sync: current test case was null”
Title: Message Title Magnus Lindstedt commented on JENKINS-17277 Re: Jenkins iOS job broken because “FATAL: Log statements out of sync: current test case was null” I agree, we have the same problem: "FATAL: Log statements out of sync: current test case was null" This occurs on XCode plugin 1.4.9 and it doesn't seem fixed on newer versions 1.4.11 There seems to be a person who has made his own fork to solve the problem when the message says: ”DEBUG: Log statements out of sync”, i.e DEBUG instead of FATAL... http://stackoverflow.com/a/15725083 I haven't tested this though, but anyone here on Jenkins support can maybe take a look at the solution. 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-39620) Saving a job with Active Choice 1.4 parameters after upgrade to v1.5 resets scriptlet parameters
Title: Message Title Bruno P. Kinoshita stopped work on JENKINS-39620 Change By: Bruno P. Kinoshita Status: In Progress Open 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-39571) Jenkins doesn't start after plugin update
Title: Message Title M U commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update Oleg Nenashev: I don't think it is a duplicate of your mentioned ticket because I don't see a similar picture. Regarding your second question about the plugins: I can not tell you, it were about 20 (Git, Copy Artifact, Credentials, etc.). The problem occurs since a couple of month every time when doing an update of either plugins or Jenkins itself. I assume it is more likely that the problem is related to my environment rather than Jenkins. I have no idea about the Java exception, I just followed these instructions: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging Jesse Glick: is it your typical workflow to close a ticket instead of providing further help for solving the issue? Definitely great for the monthly statistic about the resolved issues, but quite poor from the user's perspective. 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-26178) Ability to run docker-exec etc. from a workflow
Title: Message Title
James Hogarth reopened an issue
This was marked resolved but then after that moved to docker workflow where there is no capability to use exec on a running container ... Since docker.inside does the volume mounting behaviour and overrides ENTRYPOINT to cat it messes with things like testing a service that relies on systemd It should be possible to have a workflow similar to: docker.build('customdocker') docker.image('customdocker').withRun { it.exec("bash -c 'ps -efc ; id -a ; hostname'") } This would have Container.exec() as a method to run docker exec against the container object. As an alternative to extending the container object (which would need the it in the closure above being a little messy, but does mean it'd work with docker.run() ) adding exec alongside inside which runs each step via exec instead and doesn't override the entrypoint would be in line with other use.
Jenkins / JENKINS-26178
Ability to run docker-exec etc. from a workflow
Change By:
James Hogarth
Resolution:
Fixed
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Tommy Tynjä commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin Moving tasks out of scope for this ticket. See if a meta task connection can be added between stages. 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-39619) TFS plugin doesn't check out code writable
Title: Message Title Righardt Marais updated an issue Jenkins / JENKINS-39619 TFS plugin doesn't check out code writable Change By: Righardt Marais We have an issue where we copy files when we build as pre/post build process. The new version of Jenkins and the tfs version 5.2.1 does nto not leave workspace writable files in the workspace . Thus copy processes that overwrite files fail.The older Jenkins and TFS 3.2.0 did do this and all our build processes worked.Can the ability to select writable or not checkbox be added fro for us who need it? Otherwise we need to go fiddle with Attrib statements after Code get action. 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-39668) Attempts to copy files across jobs.
Title: Message Title Anders Hoglund edited a comment on JENKINS-39668 Re: Attempts to copy files across jobs. Problem seems to have been introduced Nov 9 in a plugin update. Job 971 fails, prev job 970 is OK, only job relative oaths paths here: http://andwho.sytes.net:8080/job/BorisB_BetaFlight/670/warnings27Result/ 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-39668) Attempts to copy files across jobs.
Title: Message Title Anders Hoglund commented on JENKINS-39668 Re: Attempts to copy files across jobs. Problem seems to have been introduced Nov 9 in a plugin update. Job 971 fails, prev job 970 is OK, only job relative oaths here: http://andwho.sytes.net:8080/job/BorisB_BetaFlight/670/warnings27Result/ 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-23049) Fails with "ERROR: Publisher jenkins.plugins.jclouds.blobstore.BlobStorePublisher aborted due to exception java.lang.IllegalArgumentException: contentLength must be set, streami
Title: Message Title SCM/JIRA link daemon commented on JENKINS-23049 Re: Fails with "ERROR: Publisher jenkins.plugins.jclouds.blobstore.BlobStorePublisher aborted due to exception java.lang.IllegalArgumentException: contentLength must be set, streaming not supported" Code changed in jenkins User: Fritz Elfert Path: jclouds-plugin/src/main/java/jenkins/plugins/jclouds/blobstore/BlobStoreProfile.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/blobstore/BlobStorePublisher.java http://jenkins-ci.org/commit/jclouds-plugin/13fa3324926ff51ec2e1cfb7bda1d41cd282ce74 Log: Fixed JENKINS-23049 Better error handling in BlobStore upload Compare: https://github.com/jenkinsci/jclouds-plugin/compare/4170abbd4367...13fa3324926f 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-23049) Fails with "ERROR: Publisher jenkins.plugins.jclouds.blobstore.BlobStorePublisher aborted due to exception java.lang.IllegalArgumentException: contentLength must be set, streami
Title: Message Title Fritz Elfert assigned an issue to Fritz Elfert Jenkins / JENKINS-23049 Fails with "ERROR: Publisher jenkins.plugins.jclouds.blobstore.BlobStorePublisher aborted due to exception java.lang.IllegalArgumentException: contentLength must be set, streaming not supported" Change By: Fritz Elfert Assignee: Fritz Elfert 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-23049) Fails with "ERROR: Publisher jenkins.plugins.jclouds.blobstore.BlobStorePublisher aborted due to exception java.lang.IllegalArgumentException: contentLength must be set, streami
Title: Message Title Fritz Elfert resolved as Fixed Should be fixed in git now. Jenkins / JENKINS-23049 Fails with "ERROR: Publisher jenkins.plugins.jclouds.blobstore.BlobStorePublisher aborted due to exception java.lang.IllegalArgumentException: contentLength must be set, streaming not supported" Change By: Fritz Elfert Status: Open Resolved 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,
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Simon Norra commented on JENKINS-38641 Re: Milestone step fails to pass due to deleted/future builds having passed I did face a very similar issue. In our project we create pipeline jobs per branch with Job DSL for a lot of microservice projects. We are using the milestone plugin as well and were very happy with this. Accidentally a change to our Job DSL script caused the seed job to delete all pipeline jobs. After fixing the issue the jobs were created again, causing all jobs to fail, because they were going to start at build number 1. The output looks like this [Pipeline] milestone Trying to pass milestone 1 Canceled since build #6 already got here [Pipeline] End of Pipeline To reproduce this: Create a job named "test-pipeline" add: stage "BUILD" echo "I do something" stage "RELEASE" milestone 1 input message: 'Do you want to release me?', ok: 'Go, release, go!' milestone 2 echo "Yes, I am released!" Just try the job a few times and accept the input prompt The milestone plugin behaves as expected Now delete the job Now create the job again, with exactly the same name and pipeline DSL script Start the job Now the job fails because the build counter is not reset and the job "thinks" the build is older than a previous one of the first, deleted job This currently makes the usage of the milestone plugin useless for us. Or is there anything we can do about it? Thank you
[JIRA] (JENKINS-39505) JClouds plugin fails on Jenkins v2.28
Title: Message Title Fritz Elfert commented on JENKINS-39505 Re: JClouds plugin fails on Jenkins v2.28 Since I did not get any further feedback, in the meantime, I have released jclouds-plugin v2.9 which runs fine here with 2.28. Maybe you want to give that one a try. 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-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title Markus May commented on JENKINS-39664 Re: Docker builds do not work with Kubernetes Pipeline plugin Uh, okay. I have done all the mentioned changes, and still get the error. I even un-installed the "normal" docker-plugin and the docker-step-plugin, still to no avail. Whom should I assign this issue to? 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-22178) Publish artifacts to Jclouds Cloud Storage - cannot publish on failure
Title: Message Title Fritz Elfert started work on JENKINS-22178 Change By: Fritz Elfert Status: Open In Progress 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-39571) Jenkins doesn't start after plugin update
Title: Message Title Oleg Nenashev commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update > Regarding your second question about the plugins: I can not tell you, it were about 20 (Git, Copy Artifact, Credentials, etc.) I recommend to install https://wiki.jenkins-ci.org/display/JENKINS/Support+Core+Plugin and to upload the support bundle generated by it. It should provide us all information we may need. > Jesse Glick: is it your typical workflow to close a ticket instead of providing further help for solving the issue? Definitely great for the monthly statistic about the resolved issues, but quite poor from the user's perspective. No, it's not common. We sometimes close issues as Incomplete if the requester does not provide the required info and then does not respond to pings, but here is another case. Jess just did a mistake, but please do not be offensive/sarcastic. It does not help anyone 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-39589) Default pod settings in 0.9 make no sens
Title: Message Title
Carlos Sanchez commented on JENKINS-39589
Re: Default pod settings in 0.9 make no sens
It shouldn't have changed, and specifically the jnpl container should have
${computer.jnlpmac} ${computer.name}
as args https://github.com/carlossg/jenkins-kubernetes-plugin/issues/7
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-39589) Default pod settings in 0.9 are wrong
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-39589 Default pod settings in 0.9 are wrong Change By: Carlos Sanchez Summary: Default pod settings in 0.9 make no sens are wrong 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-25340) lost trend history after skipping build
Title: Message Title
Daniil Ivanov edited a comment on JENKINS-25340
Re: lost trend history after skipping build
This is caused by having non-sequential build numbers in build directory for your job jenkins/jobs/${JOB_NAME}/builds.For example, you have builds 1 2 3 5 6 7, then trend results will show only builds 5 6 7 because build 4 is missing.To workaround this I've created a script:{ color:#205081} { color:red} #!/bin/shmax=3700last_dir=1for cur_dir in $(seq 1 $max)do if [ -d "$cur_dir" ]; thenif [ $(expr $cur_dir - $last_dir) -gt 1 ]; then new_dir=$(expr $last_dir + 1) echo moving $cur_dir to $new_dir mv $cur_dir $new_dir last_dir=$new_direlse last_dir=$cur_dirfi fidone {color } {color }which moves builds down to fill the gaps. After running the script you still need to edit jenkins/jobs/${JOB_NAME}/nextBuildNumber to place a new number and restart Jenkins. Then after next successful build trend result will be complete again.
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-25340) lost trend history after skipping build
Title: Message Title
Daniil Ivanov commented on JENKINS-25340
Re: lost trend history after skipping build
This is caused by having non-sequential build numbers in build directory for your job jenkins/jobs/$ {JOB_NAME}/builds. For example, you have builds 1 2 3 5 6 7, then trend results will show only builds 5 6 7 because build 4 is missing. To workaround this I've created a script: {{#!/bin/sh max=3700 last_dir=1 for cur_dir in $(seq 1 $max) do if [ -d "$cur_dir" ]; then if [ $(expr $cur_dir - $last_dir) -gt 1 ]; then new_dir=$(expr $last_dir + 1) echo moving $cur_dir to $new_dir mv $cur_dir $new_dir last_dir=$new_dir else last_dir=$cur_dir fi fi done }} which moves builds down to fill the gaps. After running the script you still need to edit jenkins/jobs/${JOB_NAME} /nextBuildNumber to place a new number and restart Jenkins. Then after next successful build trend result will be complete again.
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-6819) Jobs are triggered twice occasionally
Title: Message Title Tomas Westling commented on JENKINS-6819 Re: Jobs are triggered twice occasionally I have seen this happen in Jenkins 1.651.3, however, only when the Jenkins master is under heavy CPU load. Normally, everything works as it should, but on certain times when the Jenkins master CPU is running on max, we see two downstream builds of one project started, both builds pointing to the same parent build. This is done using the conditional build step + parameterized trigger and a schedule for the parent project. 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-20996) Generate Key Pair button doesn't work.
Title: Message Title Fritz Elfert closed an issue as Fixed Out of date. There is no "Generate Keypair" button anymore. All credentials and key-pairs are now managed by the Jenkin's default credentials framework. Jenkins / JENKINS-20996 Generate Key Pair button doesn't work. Change By: Fritz Elfert 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
[JIRA] (JENKINS-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title Ioannis Canellos assigned an issue to Jesse Glick Jenkins / JENKINS-39664 Docker builds do not work with Kubernetes Pipeline plugin Change By: Ioannis Canellos Assignee: Ioannis Canellos Jesse Glick 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-37987) Image.inside fails for images specifying ENTRYPOINT
Title: Message Title
James Hogarth commented on JENKINS-37987
Re: Image.inside fails for images specifying ENTRYPOINT
It's not much nicer but as a workaround you can do: def container = docker.image('thinggoeshere').withRun('--') { con -> sh "docker exec $ {container.id} " } This then has the same behavior as docker.image().inside() as before with ENTRYPOINT being executed (so things like systemd or a similar reaper will run) ... There's also JENKINS-26178 of course to be able to exec in a running container which would work around this, if it gets implemented.
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-37987) Image.inside fails for images specifying ENTRYPOINT
Title: Message Title
James Hogarth edited a comment on JENKINS-37987
Re: Image.inside fails for images specifying ENTRYPOINT
It's not much nicer but as a workaround you can do: {code:java} def container = docker.image(' thinggoeshere ').withRun('--') { con -> sh "docker exec ${container.id} "} {code} This then has the same behavior as docker.image().inside() as before with ENTRYPOINT being executed (so things like systemd or a similar reaper will run) ...There's also JENKINS-26178 of course to be able to exec in a running container which would work around this, if it gets implemented.
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-37987) Image.inside fails for images specifying ENTRYPOINT
Title: Message Title
James Hogarth edited a comment on JENKINS-37987
Re: Image.inside fails for images specifying ENTRYPOINT
It's not much nicer but as a workaround you can do:{code:java} def container = docker.image('').withRun('--') { con -> sh "docker exec ${ container con .id} "}{code}This then has the same behavior as docker.image().inside() as before with ENTRYPOINT being executed (so things like systemd or a similar reaper will run) ...There's also JENKINS-26178 of course to be able to exec in a running container which would work around this, if it gets implemented.
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-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title Ioannis Canellos commented on JENKINS-39664 Re: Docker builds do not work with Kubernetes Pipeline plugin I assigned it to Jesse Glick. He would know better if this needs to be assigned to someone else. 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-39665) Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin
Title: Message Title Java Dev updated an issue Jenkins / JENKINS-39665 Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin Change By: Java Dev Environment: - Operating System: Ubuntu Server 14.04 LTS 64Bit- Jenkins Version: 2.20- Active Choices Plugin version: 1.40- Java(TM) SE Runtime Environment: (build 1.8.0_101-b13)- Not run in a container.- Debian install- Firefox 49.0.2- Chrome Version 54.0.2840.71 (64-bit) 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-39667) PIpeline job ignores custom workspace location
Title: Message Title
Dmitriy Belyaev created an issue
Jenkins / JENKINS-39667
PIpeline job ignores custom workspace location
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2016/Nov/11 11:34 AM
Environment:
Windows 7, x64 Jenkins 2.19.2 Pipeline 2.4
Priority:
Major
Reporter:
Dmitriy Belyaev
After last update (not sure which one, everything worked last time on 4. nov 2016) pipeline job began to use local jenkins directory (c:/Users/jenkins/.jenkins) for workspaces completely ignoring settings set under: "Manage Jenkins / Worspace Root DIrectory" and "Manage Jenkins / Build Record Root Directory", which are configured as follow: Workspace Root Directory = d:/jenkins/ws/$ {ITEM_FULLNAME}/work Build Record Root Directory = d:/jenkins/ws/${ITEM_FULLNAME} /builds
Add Comment
[JIRA] (JENKINS-39668) Attempts to copy files across jobs.
Title: Message Title Anders Hoglund created an issue Jenkins / JENKINS-39668 Attempts to copy files across jobs. Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2016/Nov/11 11:34 AM Environment: Ubuntu 16.04LTS Priority: Major Reporter: Anders Hoglund The warnings-plugin seems to access files and tries to make copies accross job boundries. Noticed this when new files pulled in one job are not yet available in the other, then I get a lot of false warnings added to the statistics. The current job name is "BorisB_BetaFlight" and from there the warnings-plugin tries to access files in a job named "AndWho_Betaflight_buildsystem" See it all here: http://andwho.sytes.net:8080/job/BorisB_BetaFlight/697/warnings27Result/source.-8247652556134220142/#16 01 Copying the source file '/var/lib/jenkins/jobs/AndWho_Betaflight_buildsystem/workspace/src/test/./src/main/target/KAKUTEF4-V1/target.c' from the workspace to the build folder 'f16d8a0.tmp' on the Jenkins master failed. 02 Is the file '/var/lib/jenkins/jobs/AndWho_Betaflight_buildsystem/workspace/src/test/./src/main/target/KAKUTEF4-V1/target.c' a valid filename? 03 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]//var/lib/jenkins/jobs/AndWho_Betaflight_buildsystem/workspace/src/test/./src/main/target/KAKUTEF4-V1/target.c' 04 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace//var/lib/jenkins/jobs/AndWho_Betaflight_buildsystem/workspace/src/test/./src/main/target/KAKUTEF4-V1/target.c' 05
[JIRA] (JENKINS-39669) Builds fail when loading jenkins.util.SystemProperties caused by java.lang.NoClassDefFoundError: javax/servlet/ServletContextListener
Title: Message Title Robert Klaus created an issue Jenkins / JENKINS-39669 Builds fail when loading jenkins.util.SystemProperties caused by java.lang.NoClassDefFoundError: javax/servlet/ServletContextListener Issue Type: Bug Assignee: Unassigned Components: core, maven-plugin Created: 2016/Nov/11 11:52 AM Environment: Jenkins 2.19.1, 2.19.2 java.version 1.8.0_112 java.vm.vendor Oracle Corporation java.vm.version 25.112-b15 os.arch amd64 os.name Linux BUILD_TIMESTAMP 2016_1034 Maven 3.3.9 Priority: Blocker Reporter: Robert Klaus We have a similar exception as in JENKINS-35184 but this happens with builds only on master. In the hope that it is fixed we upgraded to 2.19.2 but it didn't help. The exception occurs on a random basis and cannot be pinpointed to a specific build, plugin, time,.. When it happens, all builds after that tend to fail as well. We currently have to do a restart of Jenkins on a daily basis and sometimes multiple times. Restarting Jenkins is the only workaround we currently have and is growing into a pain especially when we are releasing. This issue is a blocker for us. Our setup is: one master Jenkins running mostly all builds one Windows slave for running selenium tests most builds are run with Maven using the Maven Project Type job (seems to be important) StackTrace from the build logs:
[JIRA] (JENKINS-38734) RTC environment variables to set
Title: Message Title Fabian Güttge closed an issue as Fixed Problems vanished after update Jenkins / JENKINS-38734 RTC environment variables to set Change By: Fabian Güttge 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/d/optout.
[JIRA] (JENKINS-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title Elmar Weber commented on JENKINS-35246 Re: Kubernetes nodes not getting deleted when a pipeline job fails To clarify: The pods are terminated and deleted in kubernetes the jenkins slave reference of them in Jenkins is not deleted when they are terminated and deleted in kubernetes 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-38937) GitHub API cache is not working
Title: Message Title Kirill Merkushev commented on JENKINS-38937 Re: GitHub API cache is not working You can check that cache is used by following steps: 1. Click on "Reregister hooks for all jobs" 2. Check that there is a folder in cache: $ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/ 796K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/76c844e5 800K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/ 3. Set cache size to 0, then save global config 4. Now cache should be cleared: $ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/ 4.0K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/ 5. Set cache to any positive num back and resave global config. Then check steps 1-2. Then please write results 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
[JIRA] (JENKINS-39571) Jenkins doesn't start after plugin update
Title: Message Title Oleg Nenashev commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update Yes, it would be nice 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-38937) GitHub API cache is not working
Title: Message Title
Kirill Merkushev edited a comment on JENKINS-38937
Re: GitHub API cache is not working
You can check that cache is used by following steps:1. Click on "Reregister hooks for all jobs"2. Check that there is a folder in cache:{code}$ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/796K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/76c844e5800K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/{code}3. Set cache size to 0, then save global config4. Now cache should be cleared:{code}$ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/4.0K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/{code}5. Set cache to any positive num back and resave global config. Then check steps 1-2.Then please write results . Also please provide full list of plugins (maybe some of them eat your limits without using cache from GitHub plugin's client?)
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-39670) Jenkins changes workspace layout on 2nd startup
Title: Message Title
Jens Keller created an issue
Jenkins / JENKINS-39670
Jenkins changes workspace layout on 2nd startup
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Nov/11 12:22 PM
Priority:
Major
Reporter:
Jens Keller
Used Jenkins version: 2.19.1, but I'm pretty sure this behavior is also present in older jenkins versions Steps to reproduce:
Download the jenkins.war file
Make sure you have an empty/not existing ~/.jenkins (or whatever JENKINS_HOME directory is used)
From the directory where you downloaded the .war file, run `java -Djenkins.install.runSetupWizard=false -jar jenkins.war`
When Jenkins is started, go to Manage Jenkins -> Configure System and click the "Advanced" button underneath the home directory setting at the top of the page
Observation: the workspace root directory is specified as`$ {JENKINS_HOME}/workspace/${ITEM_FULLNAME}`, as it is documented on https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins - Cancel the process - Restart Jenkins and again, go to the central configuration - Observation: the workspace root directory suddenly changed to `${ITEM_ROOTDIR}/workspace` This behavior is extremely odd and creates a lot of confusion and wastes people's time, as some Jenkins servers/jobs have the one layout, and some have the other layout, depending on when the jobs where created and whether Jenkins was re-started in between or not. Also I want to raise that the documentation is contradicting: - in the built-in documentation of the config option, it says `The default value is ${ITEM_ROOTDIR}/workspace.` - in the above mentioned wiki page it indicates that
[JIRA] (JENKINS-39571) Jenkins doesn't start after plugin update
Title: Message Title M U commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update Okay, the plugin is installed. What would be the most helpful workflow for you? Create an initial bundle, do the update of some plugins for enforce the restart problem and create a second bundle afterwards? 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-38734) RTC environment variables to set
Title: Message Title Fabian Güttge commented on JENKINS-38734 Re: RTC environment variables to set I updated to Jenkins ver. 2.19.2 Pipeline 2.4 Pipeline: Groovy 2.23 Pipeline: Job 2.9 and this solved the issue for me. I suspect that this issue is connected to JENKINS-30910 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-39673) View-related CLI commands should also work for views on folder level
Title: Message Title arostfx created an issue Jenkins / JENKINS-39673 View-related CLI commands should also work for views on folder level Issue Type: Improvement Assignee: Unassigned Components: cloudbees-folder-plugin Created: 2016/Nov/11 2:52 PM Priority: Major Reporter: arostfx Jenkins supports a variety of CLI commands for view maintenance: add-job-to-view create-view delete-view get-view remove-job-from-view update-view Currently, those commands cannot be used to manage views that are defined on folder level. For users that rely on automated management of views, this is a major obstacle when introducing folders – they basically need to stop using the CLI commands and resport to custom groovy code for folder maintenance. Therefore, it will be useful to extend the above CLI commands so they also support views that exist on folder level.
[JIRA] (JENKINS-39614) Sort failed jobs first
Title: Message Title Tommy Tynjä resolved as Fixed Jenkins / JENKINS-39614 Sort failed jobs first Change By: Tommy Tynjä Status: Open Resolved 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/d/optout.
[JIRA] (JENKINS-39614) Sort failed jobs first
Title: Message Title Tommy Tynjä commented on JENKINS-39614 Re: Sort failed jobs first PR 215 merged: 9dcfe9aae5ee8c70ccdf2302230fcae8b4ac8ab3 Will be part of next release. Thank you Mikael Sundberg for your contribution! 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-39672) Token-macro PCT issues against 2.91.x
Title: Message Title Andres Rodriguez created an issue Jenkins / JENKINS-39672 Token-macro PCT issues against 2.91.x Issue Type: Bug Assignee: Andres Rodriguez Components: token-macro-plugin Created: 2016/Nov/11 2:17 PM Environment: Jenkins 2.19.2 Token Macro 2.0 Priority: Minor Reporter: Andres Rodriguez Because of JENKINS-21486 token-macro fail the PCT scenario against 2.19.x. Proposed fix is to bring the needed test dependencies to the POM. Add Comment
[JIRA] (JENKINS-38920) JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38920 Re: JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiManifestSpec.groovy src/test/resources/org/jenkinsci/gradle/plugins/jpi/test.mf http://jenkins-ci.org/commit/gradle-jpi-plugin/022c059aba2dd9f4322b4624e03efb696e46b071 Log: fixed problem with missing Plugin-Class attribute in generated manifest [FIXES JENKINS-38920] 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-39672) Token-macro PCT issues against 2.91.x
Title: Message Title Andres Rodriguez updated JENKINS-39672 Jenkins / JENKINS-39672 Token-macro PCT issues against 2.91.x Change By: Andres Rodriguez Status: In Progress Review 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-39571) Jenkins doesn't start after plugin update
Title: Message Title M U updated an issue Jenkins / JENKINS-39571 Jenkins doesn't start after plugin update Change By: M U Attachment: support_2016-11-11_12.58.39.zip Attachment: support_2016-11-11_13.48.03.zip 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-39671) PageLoading indicator not working on pipelines page
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-39671 PageLoading indicator not working on pipelines page Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/11 1:58 PM Priority: Major Reporter: Tom FENNELLY The does not seem to be clicking into action on the pipelines page, with the result that the loading indicator just stays in a loading state forever, which looks a bit weird. I had a quick look at it but can't make any sense of it. Maybe someone else can. Seems like PageLoading is not activated on the page at all and so the LoadingIndicator show and hide functions are never called. That's just from a quick scan though, so not really sure. Add Comment
[JIRA] (JENKINS-39571) Jenkins doesn't start after plugin update
Title: Message Title M U commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update Please take a look at the following files: support_2016-11-11_12.58.39.zip support_2016-11-11_13.48.03.zip What I did: Created the first bundle Updated some plugins and activated "restart Jenkins after installation" Jenkins tried to restart, but stucks in "Please wait while Jenkins is getting ready to work..." Restarted Jenkins' Windows service Created the second bundle 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-35013) PluginManager not able to update
Title: Message Title Sahil Shaikh commented on JENKINS-35013 Re: PluginManager not able to update I am facing the same issue with Jenkins 2.19.2. java.io.IOException: Could not find JSON in http://updates.jenkins-ci.org/update-center.json?id=default=2.19.2 Jenkins is behind corporate proxy and the HTTP Proxy settings gives "Siccess" on Validate Proxy 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-39614) Sort failed jobs first
Title: Message Title Tommy Tynjä assigned an issue to Mikael Sundberg Jenkins / JENKINS-39614 Sort failed jobs first Change By: Tommy Tynjä Assignee: Patrik Boström Mikael Sundberg 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-39668) Attempts to copy files across jobs.
Title: Message Title Anders Hoglund edited a comment on JENKINS-39668 Re: Attempts to copy files across jobs. Problem seems to have been introduced Nov 9 in a plugin update. Job 971 671 fails, prev job 970 670 is OK, only job relative paths here: http://andwho.sytes.net:8080/job/BorisB_BetaFlight/670/warnings27Result/ 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-39672) Token-macro PCT issues against 2.91.x
Title: Message Title Andres Rodriguez started work on JENKINS-39672 Change By: Andres Rodriguez Status: Open In Progress 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-38920) JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38920 Re: JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiManifestSpec.groovy src/test/resources/org/jenkinsci/gradle/plugins/jpi/test.mf http://jenkins-ci.org/commit/gradle-jpi-plugin/65547ed4b757b1a476a198c9a5e5d9113be38b80 Log: Merge pull request #81 from daspilker/JENKINS-38920 JENKINS-38920 fixed problem with missing Plugin-Class attribute in generated manifest Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/2acb996a417f...65547ed4b757 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-38920) JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38920 JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned Change By: SCM/JIRA link daemon Status: Open Resolved 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/d/optout.
[JIRA] (JENKINS-39611) ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step
Title: Message Title Jean-Christophe Sirot commented on JENKINS-39611 Re: ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step I reviewed this issue and it does not seems to be a bug but it shows that the field names and documentation have to be improved. The "file path" field when the file radio button is selected accepts a comma separated list of hosts. Note that the host list must not contain spaces (before or after the comma) since the ansible-playbook command seems to consider everything between the commas to be a hostname. Also the "inline content" is used to create an inventory file on the fly and avoid the creation of such a file from a script for instance. 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-38715) Container instance cannot be empty error
Title: Message Title Nando Sola commented on JENKINS-38715 Re: Container instance cannot be empty error I'm getting the same error when the desired capacity of the autoscaling group is set to zero. Our ideal use case would be that the plugin launched a new EC2 instance before deploying the task. This is useful in terms of not having an idle instace waiting for tasks. 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-38715) Container instance cannot be empty error
Title: Message Title Nando Sola edited a comment on JENKINS-38715 Re: Container instance cannot be empty error I'm getting the same error when the desired capacity of the autoscaling group is set to zero. Our ideal use case would be that the plugin launched a new EC2 cluster instance before deploying the task. This is useful in terms of not having an idle EC2 instace waiting for tasks. 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-38991) NullPointerException in logging of DependencyCheckExecutor
Title: Message Title Stephan Krull reopened an issue @Steve Springett: After installing version 1.4.4 and running the build we still have a failure, see stacktrace 09:24:30 [DependencyCheck] Scanning: /var/lib/jenkins/jobs/AuthServer/workspace/authserver/build/libs/authserver.jar 09:24:31 [DependencyCheck] Analyzing Dependencies 09:26:50 [DependencyCheck] One or more exceptions were thrown while executing Dependency-Check 09:26:50 [DependencyCheck] Exception Caught: java.util.ConcurrentModificationException 09:26:50 ERROR: Build step failed with exception 09:26:50 java.lang.NullPointerException 09:26:50 at org.jenkinsci.plugins.DependencyCheck.DependencyCheckExecutor.performBuild(DependencyCheckExecutor.java:109) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$1.call(AbstractDependencyCheckBuilder.java:90) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$1.call(AbstractDependencyCheckBuilder.java:87) 09:26:50 at hudson.remoting.LocalChannel.call(LocalChannel.java:45) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder.perform(AbstractDependencyCheckBuilder.java:87) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.DependencyCheckBuilder.perform(DependencyCheckBuilder.java:209) 09:26:50 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 09:26:50 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) 09:26:50 at hudson.model.Build$BuildExecution.build(Build.java:205) 09:26:50 at hudson.model.Build$BuildExecution.doRun(Build.java:162) 09:26:50 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 09:26:50 at hudson.model.Run.execute(Run.java:1720) 09:26:50 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 09:26:50 at hudson.model.ResourceController.execute(ResourceController.java:98) 09:26:50 at hudson.model.Executor.run(Executor.java:404) 09:26:50 Build step 'Invoke OWASP Dependency-Check analysis' marked build as failure The NullPointerException still arises from the "for" loop. ec.getExceptions() seems to return null objects. Can you fix this? Jenkins / JENKINS-38991 NullPointerException in logging of DependencyCheckExecutor Change By: Stephan Krull Resolution: Fixed Status: Closed Reopened
[JIRA] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Tommy Tynjä commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin Task connections implemented. After discussions among the maintainers we decided to cut the scope and focus on delivering this feature as an MVP. Only code review and possible refactoring improvements left to consider before delivery. 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.
