[JIRA] (JENKINS-36988) no information regarding using influx-db with jenkins pipelines
Title: Message Title Aleksi Simell updated an issue Jenkins / JENKINS-36988 no information regarding using influx-db with jenkins pipelines Change By: Aleksi Simell Comment: Release 1.4 is now available with pipeline support. The plugin can be used as a step in the build. However, since pipelines have no post-build actions, some of the data (build status, build duration) are not sent to influx or might be incorrect because the build is not actually finished when the plugin runs. If you want all data to be available, the only option is to configure it to the jobs separately. 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-36988) no information regarding using influx-db with jenkins pipelines
Title: Message Title Aleksi Simell closed an issue as Done Release 1.4 is now available with pipeline support. The plugin can be used as a step in the build. However, since pipelines have no post-build actions, some of the data (build status, build duration) are not sent to influx or might be incorrect because the build is not actually finished when the plugin runs. If you want all data to be available, the only option is to configure it to the jobs separately. Jenkins / JENKINS-36988 no information regarding using influx-db with jenkins pipelines Change By: Aleksi Simell Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36988) no information regarding using influx-db with jenkins pipelines
Title: Message Title Aleksi Simell commented on JENKINS-36988 Re: no information regarding using influx-db with jenkins pipelines Release 1.4 is now available with pipeline support. The plugin can be used as a step in the build. However, since pipelines have no post-build actions, some of the data (build status, build duration) are not sent to influx or might be incorrect because the build is not actually finished when the plugin runs. If you want all data to be available, the only option is to configure it to the jobs separately. 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-37199) Developer can see how long ago the run finished executing on the dashboard
Title: Message Title Michael Neale commented on JENKINS-37199 Re: Developer can see how long ago the run finished executing on the dashboard The running job will show the time since started in a hover state (popover thing). 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-22547) Git timeout setting does not work for checkout
Title: Message Title Florian Manschwetus commented on JENKINS-22547 Re: Git timeout setting does not work for checkout Is this also fixed in the beta, needed for submodule credentials? 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-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title
Tomas Bjerre commented on JENKINS-37196
Re: DSL for Violation Comments to GitHub Plugin
You need to add violationConfigs like this:
violationsToGitHubRecorder {
createSingleFileComments(true)
createCommentWithAllSingleFileComments(false)
repositoryName(repoName)
repositoryOwner(‘jen1')
password('')
username('')
oAuth2Token('')
pullRequestId('$
{ghprbPullId}
')
gitHubUrl('https://github.inmobi.com/api/v3')
commentOnlyChangedContent(true)
usernamePasswordCredentialsId('false')
useOAuth2Token(false)
useUsernamePassword(false)
useUsernamePasswordCredentials(true),
violationConfigs: [
new ViolationConfig(Reporter.FINDBUGS, ".*/findbugs.*\\.xml\$")
]
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37199) Developer can see how long ago the run finished executing on the dashboard
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37199 Developer can see how long ago the run finished executing on the dashboard Change By: James Dumay In Scope* When the card is representing a completed state it shows how long it ran for * Update the styling so that it groups branch, commit and complete state together with a bias to the right hand side. 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-37199) Developer can see how long ago the run finished executing on the dashboard
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37199 Developer can see how long ago the run finished executing on the dashboard Issue Type: Story Assignee: Unassigned Attachments: Success.png Components: blueocean-plugin Created: 2016/Aug/05 4:52 AM Priority: Minor Reporter: James Dumay In Scope When the card is representing a completed state it shows how long it ran for Add Comment
[JIRA] (JENKINS-37198) Dashboard improvements to show time since activity
Title: Message Title James Dumay resolved as Fixed Ben Walding we've opted to add this information to the favourite cards instead of the table. See JENKINS-37199 Jenkins / JENKINS-37198 Dashboard improvements to show time since activity Change By: James Dumay 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.
[JIRA] (JENKINS-27120) Make JacocoPublisher a SimpleBuildStep
Title: Message Title Martin Heinzerling commented on JENKINS-27120 Re: Make JacocoPublisher a SimpleBuildStep This commits are in the master, it just a kind of messed up in the history. Either use the current master for the minimal pipeline support or if mheinzerling_2.1.0 a try, where I already add some improvements. 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-37198) Dashboard improvements to show time since activity
Title: Message Title Michael Neale commented on JENKINS-37198 Re: Dashboard improvements to show time since activity For design consideration. 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-37198) Dashboard improvements to show time since activity
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-37198 Dashboard improvements to show time since activity Change By: Michael Neale Some feedback from talking to ben, was that the dashboard was a bit anemic with recent activity. As an ops manager, he often lands on dashboard and is curious about recent activity (which he may not have been involved with). Favouriting pipelines helps, but even the cards could do with more information on the most recent build activity (ie how long ago, and what result was). The attached images show some suggestions of where times since last build could go. (Certainly the card has room). It would make sense to also include that it was a success or not (ie show "last failure" or "last success"). Relative time is preferred. 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
[JIRA] (JENKINS-37198) Dashboard improvements to show time since activity
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-37198 Dashboard improvements to show time since activity Issue Type: Story Assignee: James Dumay Attachments: Screen Shot 2016-08-05 at 1.50.21 PM.png, Screen Shot 2016-08-05 at 1.50.33 PM.png Components: blueocean-plugin Created: 2016/Aug/05 3:52 AM Priority: Minor Reporter: Michael Neale Some feedback from talking to ben, was that the dashboard was a bit anemic with recent activity. Favouriting pipelines helps, but even the cards could do with more information on the most recent build activity (ie how long ago, and what result was). The attached images show some suggestions of where times since last build could go. (Certainly the card has room). It would make sense to also include that it was a success or not (ie show "last failure" or "last success"). Relative time is preferred. Add Comment
[JIRA] (JENKINS-37197) Allow custom configuration file name
Title: Message Title Matt Stevens commented on JENKINS-37197 Re: Allow custom configuration file name I tried to set it up with VirtualBox on a server, to find my VirtualBox configuration followed me as well, which solved the Jenkins problem and recreated it as a VirtualBox problem. However, that aside, we are trying to reduce the learning load on these students to the bare minimum needed for the course (A practical 3rd year course to experience Agile development with industry clients. Prescribed tools are GitLab and Jenkins while the twenty projects include embedded systems, IoT devices, SDN firewall, phone apps, management tools, a business simulator, a couple of web apps and a Zoo app). Three weeks in, we still have a handful of students that have not successfully installed Jenkins on their personal machines. Which is not a Jenkins complaint, just a reality of introducing students to new technology. 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-31487) Job status not updated in web UI during build
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-31487 Re: Job status not updated in web UI during build I did troubleshoot this. I can easily reproduce with Jenkins 1.651 and Jenkins 2.7.1 too. Here is the simplest scenario: Create a Freestyle Job Add a Shell task "sleep 10" so that you can notice the behavior of the progress bar Build the job You should see the build job progress bar refreshing and switching to complete Configure the Freestyle Job Check the "This build is parameterized" and add a String Parameter Build the job The build start and the progress bar hangs like previous screenshots shows. So seems to be related to parameterized builds. 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-37137) Cache last state of page for fast subjective loading experience
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37137 Cache last state of page for fast subjective loading experience Change By: James Dumay Google Inbox, despite it's many faults, provides a subjective fast load experience by caching some recent state of the app. Possibly using localStorage. Or perhaps they are witches, who can tell. In any case it would be a nice experience improvement. From mashing the keyboard the best description I can find on google: https://developers.google.com/web/updates/2015/11/app-shell?hl=en That is what inbox uses.*In scope** Investigate if there are benefits to taking this approach for blue ocean* Write up a short Google doc on how we could get there 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-37137) Cache last state of page for fast subjective loading experience
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37137 Cache last state of page for fast subjective loading experience Change By: James Dumay Issue Type: Story Task 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-37137) Cache last state of page for fast subjective loading experience
Title: Message Title Michael Neale commented on JENKINS-37137 Re: Cache last state of page for fast subjective loading experience Sample app with app-shell: https://github.com/GoogleChrome/application-shell/ 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-37197) Allow custom configuration file name
Title: Message Title Mark Waite commented on JENKINS-37197 Re: Allow custom configuration file name You might consider running the personal instances with Docker. They have an isolated file system and process address space and can host multiple instances on a single machine. It would also give your students experience with Docker and containers. 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-31924) GitSCMSource should offer extensions
Title: Message Title Mark Waite edited a comment on JENKINS-31924 Re: GitSCMSource should offer extensions [~adisutanto] the changelog doesn't mention specific extensions because the change made them all available. Refer to !Multi-branch-pipeline-git-extensions.png|thumbnail! 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-31924) GitSCMSource should offer extensions
Title: Message Title Mark Waite edited a comment on JENKINS-31924 Re: GitSCMSource should offer extensions [~adisutanto] the changelog doesn't mention specific extensions because the change made them all available.Refer to the attached picture for the job configuration screen !Multi-branch-pipeline-git-extensions.png|thumbnail! 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-31924) GitSCMSource should offer extensions
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-31924 GitSCMSource should offer extensions Change By: Mark Waite Attachment: Multi-branch-pipeline-git-extensions.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31924) GitSCMSource should offer extensions
Title: Message Title Mark Waite commented on JENKINS-31924 Re: GitSCMSource should offer extensions Adi Sutanto the changelog doesn't mention specific extensions because the change made them all available. 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-37197) Allow custom configuration file name
Title: Message Title Matt Stevens created an issue Jenkins / JENKINS-37197 Allow custom configuration file name Issue Type: New Feature Assignee: Unassigned Components: core Created: 2016/Aug/05 1:03 AM Environment: Jenkins 2.7 .war file Labels: installation configuration_file Priority: Blocker Reporter: Matt Stevens Use Case. I am a lecturer teaching Agile, Git and CI within a university environment. I would like students to be running individual copies of Jenkins for testing their local code on Git commit hooks and a team Jenkins repository testing code on pushing to the team Git repository (using push hooks). The Problem The university student has a single user id and profile within the university system. We have access to spare servers but find the existing student profile is used everywhere within this environment meaning the students existing ~/.jenkins configuration file is also used by the server. This is undesirable as we wish to maintain a clear seperation between personal instances of Jenkins and the teams. There are a number of potential solutions, some require credit cards to access free off-site servers, others involve engaging with other departments within the university. We need a solution that scales and can be implemented within the course, in this trimester we are running twenty projects - a number we expect will grow over time. The suggested solution Jenkins currently uses what appears to be a hard coded configuration file name. It would be a self contained solution to this use case if on installation a flag can be used to set the
[JIRA] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title
Giriraj Gujar created an issue
Jenkins / JENKINS-37196
DSL for Violation Comments to GitHub Plugin
Issue Type:
Bug
Assignee:
Tomas Bjerre
Attachments:
violation.png
Components:
violation-comments-to-github-plugin
Created:
2016/Aug/05 12:53 AM
Priority:
Minor
Reporter:
Giriraj Gujar
Hi Tomas, I hope you are doing great. I needed small info, basically it is the DSL code for "Violation Comments to GitHub Plugin“ Actually I have most of the below code: ## violationsToGitHubRecorder { createSingleFileComments(true) createCommentWithAllSingleFileComments(false) repositoryName(repoName) repositoryOwner(‘jen1') password('') username('') oAuth2Token('') pullRequestId('$ {ghprbPullId} ') gitHubUrl('https://github.inmobi.com/api/v3') commentOnlyChangedContent(true) usernamePasswordCredentialsId('false') useOAuth2Token(false) useUsernamePassword(false) useUsernamePasswordCredentials(true) ### However the problem is how to to add “pattern” part to it? so it get automatically comes up? If you see the screen shot, then there is nothing coming under pattern block? Let me know if you have any inputs to share? Thanks, Giiraj
[JIRA] (JENKINS-37195) Visiting nonexistent URLs gives 500 with stack trace instead of 404
Title: Message Title trejkaz created an issue Jenkins / JENKINS-37195 Visiting nonexistent URLs gives 500 with stack trace instead of 404 Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2016/Aug/05 12:19 AM Priority: Minor Reporter: trejkaz I was fixing warnings in a particular category. When I had finally fixed the last warning in the category, the "Next Build" link for the previous build generated a link that went to an error page: javax.servlet.ServletException: java.util.NoSuchElementException: Category by hashCode not found: 1451231946 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 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
[JIRA] (JENKINS-31039) Queue items are ephemeral leading to api users to lose track of builds.
Title: Message Title Jared Lynem commented on JENKINS-31039 Re: Queue items are ephemeral leading to api users to lose track of builds. Yeah that's the next logical step Russell, but I didn't want to propose anything high effort. For a medium-frequency job the solution would work fine for what I'm imagining is a typical use case (I just invoked a job, what's the build number?). I did this today using an extra job parameter that's a tracking guid, and the performance is fine as is (linear search of builds in descending order via rest calls) with that use case. I'm sure one could write a plugin to do the whole search server-side, too. The whole REST APi is pretty anemic and needs an overhaul, but I'm sure the devs know that. I just don't feel comfortable demanding anything from a tool that's saved our organization probably hundreds of thousands of dollars. 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-37194) Allow Tokens via Token Macro plugin
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-37194 Allow Tokens via Token Macro plugin Issue Type: Improvement Assignee: Andrew Sumner Components: inedo-proget-plugin Created: 2016/Aug/05 12:01 AM Priority: Major Reporter: Jon Starbird Allow Tokens via the Token Macros plugin, this would be very useful so that jobs can be used for multiple purposes but also so that versions can be variable defined. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-37193 inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Issue Type: Bug Assignee: Andrew Sumner Components: inedo-proget-plugin Created: 2016/Aug/04 11:51 PM Priority: Major Reporter: Jon Starbird Inedo-buildmaster-plugin component is not listed. When attempting to use the Select BuildMaster Application you get an error "Error: Unable to connect to BuildMaster. java.lang.NullPointerException: null" on the Job Configuration screen. BuildMaster configuration in Admin area is setup and Test Connection from there works. Add Comment
[JIRA] (JENKINS-35783) REST API must only be authenticated using JWT
Title: Message Title Vivek Pandey commented on JENKINS-35783 Re: REST API must only be authenticated using JWT All backend API changes are in place along with tests. More testing needs to be done though. Although its closer to ready for review for merge but we need all the UI side changes for end to end to work. Yes JWT is enabled by default and can be disabled by providing system property so its important to finish UI side changes and do a single merge. See all the fronted and backend tasks at https://github.com/jenkinsci/blueocean-plugin/pull/392. 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-31039) Queue items are ephemeral leading to api users to lose track of builds.
Title: Message Title Russell Weber commented on JENKINS-31039 Re: Queue items are ephemeral leading to api users to lose track of builds. Jared Lynem, This could be a viable option if you only have to search through a few builds. However it could mean that there are many builds to rummage through before a build is found tying up precious network and/or disk resources. I don't have any experience with the Jenkins source code it's self, only the python API, can any one speak to the ease of being able to search for the queue item in every build to match queue items? If it's the case that we can search for the queue item in the builds, is it then viable that maybe jenkins shouldn't return an error if the queue item is no longer there, but do the search it's self and then return as if the queue item still did exist? I have a feeling that is too much to ask, but if nothing more, it might help me get my hands dirty in understanding some of the lower level working of Jenkins by learning why it wouldn't. 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-36229) API for UI to honour permissions
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36229 API for UI to honour permissions Change By: Michael Neale Priority: Blocker Critical 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-36976) Ensure that the "stop" API for runs is implemented correctly
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36976 Ensure that the "stop" API for runs is implemented correctly Change By: James Dumay Priority: Critical Blocker 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-34563) Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine
Title: Message Title Giovanni Tirloni commented on JENKINS-34563 Re: Github Organization Folder Plugin does not discover new repositories after first Re-scan Organization although Webhook is working fine Reproduced issue with: Jenkins 2.16 GitHub API Plugin 1.76 GitHub Branch Source Plugin 1.8.1 GitHub Organization Folder Plugin 1.4 GitHub plugin 1.20.0 Pipeline 2.2 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-37192) Plugin does not remember preferences
Title: Message Title Tim Smith created an issue Jenkins / JENKINS-37192 Plugin does not remember preferences Issue Type: Bug Assignee: Unassigned Components: hsts-filter-plugin Created: 2016/Aug/04 10:06 PM Environment: OS X 10.11, Jenkins 2.7.1 serving directly, HSTS Filter 1.0 Priority: Major Reporter: Tim Smith After configuring "max age" to a non-default value, the plugin stops applying the HSTS header. After restarting Jenkins, the HSTS header appears again, but max-age has been reset to the default. Add Comment
[JIRA] (JENKINS-37191) Organization WebHook misses PR updates
Title: Message Title Giovanni Tirloni created an issue Jenkins / JENKINS-37191 Organization WebHook misses PR updates Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/Aug/04 9:40 PM Environment: Jenkins 2.16 GitHub API Plugin 1.76 GitHub Branch Source Plugin 1.8.1 GitHub Organization Folder Plugin 1.4 GitHub plugin 1.20.0 Pipeline 2.2 Priority: Minor Reporter: Giovanni Tirloni When the plugin creates the organization webhook, it only specifies that GH should send "Push" and "Repository" events. This causes updates to PR's to be ignored. Workaround: manually edit the organization webhook and activate updates for "Pull request" (Pull request opened, closed, reopened, edited, assigned, unassigned, labeled, unlabeled, or synchronized). Add Comment
[JIRA] (JENKINS-37164) ECS plugin does not use InstanceProfileCredentialsProvider, and cannot use IAM profile
Title: Message Title Evan Borgstrom closed an issue as Not A Defect Sorry, this is NOT a bug. It turned out to be because of: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1396760 The IAM profile does indeed work as expected. Jenkins / JENKINS-37164 ECS plugin does not use InstanceProfileCredentialsProvider, and cannot use IAM profile Change By: Evan Borgstrom Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-37011) Provide a way to write full-fledged Steps in CPS-transformed Groovy
Title: Message Title Jesse Glick updated JENKINS-37011 Jenkins / JENKINS-37011 Provide a way to write full-fledged Steps in CPS-transformed Groovy Change By: Jesse Glick Status: In Review 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-28385) Step to obtain raw contextual objects
Title: Message Title Jesse Glick commented on JENKINS-28385 Re: Step to obtain raw contextual objects Might be useful in some cases for JENKINS-37011. 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-36372) After resuming build, newly loaded scripts do not share root binding
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-36372 After resuming build, newly loaded scripts do not share root binding Change By: Jesse Glick 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-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Title: Message Title Giovanni Tirloni commented on JENKINS-34612 Re: Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..." I can confirm that once user is made owner *of the GH organization, then even with the initial errors (due to unauthenticated requests), the Webhook *is properly added if the proper credential is specified when adding the new item. 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-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Title: Message Title Giovanni Tirloni edited a comment on JENKINS-34612 Re: Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..." I can confirm that once user is made *owner *of the GH organization, then even with the initial errors (due to unauthenticated requests), the Webhook *is* properly added if the proper credential is specified when adding the new item. 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-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Title: Message Title
Giovanni Tirloni edited a comment on JENKINS-34612
Re: Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Same issue encountered on the following environment:Jenkins 2.16GitHub API Plugin 1.76GitHub Branch Source Plugin 1.8.1GitHub Organization Folder Plugin 1.4GitHub plugin 1.20.0Pipeline 2.2Steps to reproduce:1 - New Item2 - Enter GitHub organization name3 - Select "GitHub organization"4 - Click OK Details:1 - Issue happens with and without a GitHub server added to Jenkins with the proper credentials.2 - Making user an owner or admin of the GH organization does not help. Stack trace:{noformat}Aug 04, 2016 8:14:26 PM WARNING org.jenkinsci.plugins.orgfolder.github.MainLogic applyOrgFailed to register GitHub Org hook to https://github.com/crash-test-dummies (missing permissions?): {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}Aug 04, 2016 8:14:26 PM FINE org.jenkinsci.plugins.orgfolder.github.MainLogicnulljava.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"} at org.kohsuke.github.Requester.handleApiError(Requester.java:553) at org.kohsuke.github.Requester._to(Requester.java:264) at org.kohsuke.github.Requester.to(Requester.java:205) at org.kohsuke.github.GHHooks$Context.getHooks(GHHooks.java:25) at org.kohsuke.github.GHOrganization.getHooks(GHOrganization.java:276) at org.jenkinsci.plugins.orgfolder.github.MainLogic.existsHook(MainLogic.java:198) at org.jenkinsci.plugins.orgfolder.github.MainLogic.applyOrg(MainLogic.java:89) at org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl.maybeApply(ItemListenerImpl.java:41) at org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl.onUpdated(ItemListenerImpl.java:29) at hudson.model.listeners.ItemListener$3.apply(ItemListener.java:195) at hudson.model.listeners.ItemListener$3.apply(ItemListener.java:193) at hudson.model.listeners.ItemListener.forAll(ItemListener.java:167) at hudson.model.listeners.ItemListener.fireOnUpdated(ItemListener.java:193) at com.cloudbees.hudson.plugins.folder.AbstractFolder.save(AbstractFolder.java:667) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList._onModified(PersistedList.java:181) at hudson.util.PersistedList.add(PersistedList.java:72) at jenkins.branch.CustomOrganizationFolderDescriptor.newInstance(CustomOrganizationFolderDescriptor.java:109) at hudson.model.ItemGroupMixIn.createProject(ItemGroupMixIn.java:323) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:203) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:3669) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 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
[JIRA] (JENKINS-31094) Proposal: Jenkins Configuration DSL
Title: Message Title
Sam Gleske edited a comment on JENKINS-31094
Re: Proposal: Jenkins Configuration DSL
Hi all,I'd like to throw my 2 cents into this hat :). In general, I've found the most effective way to configure Jenkins is to use the [Script Console (link) |https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console] and bootstrap Jenkins and plugins via gradle.h1. Bootstrapping Jenkins via gradleBootstrapping Jenkins via gradle provides something that is currently lacking in Jenkins documentation (which I'm slowly improving over time). The idea of idempotent configurations. That is, if I bootstrap my automation scripts next year they should still be guaranteed to work. The current state of most configuration management "solutions" I've seen is this isn't the case. However, Jenkins publishes the war file and all of it's plugins in Artifactory. This offers a great platform to guarantee idempotent configurations.Here's an example of my scripts [bootstrapping Jenkins and all plugin versions via gradle (link)|https://github.com/samrocketman/jenkins-bootstrap-jervis/blob/e3f7f2e26379713e26c23af6d444f97dca0e5363/build.gradle#L47-L96].Advantages of this method:* Guaranteed to bootstrap the same way next year as it does this year.* Maven repository can be mirrored on-site in enterprises to ensure reliable bootstrapping.* It's easier to spin up test environments with the same versions of Jenkins and plugins this way (even on my own laptop).* Plugin updates and upgrades can be more safely quality tested and approved for upgrade in production.h1. "Jenkins State Machine"When it comes to configuration management and an existing Jenkins installation I've always thought of what I call a "Jenkins State Machine". The Jenkins State Machine is essentially the following:# If Jenkins is _not_ in shutdown mode, then configuration changes can occur in the Jenkins runtime.# If Jenkins is in shutdown mode, then don't make any configuration changes to Jenkins. i.e. any script which can change the runtime configuration should choose _not to change_ if Jenkins is in this state.# If Jenkins is in shutdown mode and there are jobs running, then Jenkins should not be restarted. A "restart" configuration management script should always just choose to wait to allow running jobs to finish.# If Jenkins is in shutdown and there are no jobs running, then it is safe to restart Jenkins.The above state machine can be relatively safely run, automatically, without affecting users too drastically. Something like this can be done without much human intervention as long as the state machine is adhered in all config management scripts.The above state machine still poses minor problems. Any time jobs queue up during shutdown mode, the state of the queue is discarded on restart. The Jenkins job queue could be preserved when Jenkins is gracefully restarted or gracefully shut down.h1. Configure via Script ConsoleOne of the most powerful things I've learned about Jenkins and the Script Console is that its runtime is itself the configuration. By updating the runtime, you're updating the configuration and can serialize that configuration to disk with a {{Jenkins.instance.save()}} or calling the {{save()}} method on other configuration objects.Pros:* The "Jenkins State Machine" can be adhered.* Configuration is immediately updated and the operation is as safe as clicking "Save" in the web UI.* No restart is required for trivial configuration updates via the Script Console. If the XML configuration on disk is modified then a Jenkins restart is required or executing "Reload configuration from disk". It's an intense and disruptive action.
[JIRA] (JENKINS-31094) Proposal: Jenkins Configuration DSL
Title: Message Title Sam Gleske commented on JENKINS-31094 Re: Proposal: Jenkins Configuration DSL Hi all, I'd like to throw my 2 cents into this hat . In general, I've found the most effective way to configure Jenkins is to use the Script Console and bootstrap Jenkins and plugins via gradle. Bootstrapping Jenkins via gradle Bootstrapping Jenkins via gradle provides something that is currently lacking in Jenkins documentation (which I'm slowly improving over time). The idea of idempotent configurations. That is, if I bootstrap my automation scripts next year they should still be guaranteed to work. The current state of most configuration management "solutions" I've seen is this isn't the case. However, Jenkins publishes the war file and all of it's plugins in Artifactory. This offers a great platform to guarantee idempotent configurations. Here's an example of my scripts bootstrapping Jenkins and all plugin versions via gradle (link). Advantages of this method: Guaranteed to bootstrap the same way next year as it does this year. Maven repository can be mirrored on-site in enterprises to ensure reliable bootstrapping. It's easier to spin up test environments with the same versions of Jenkins and plugins this way (even on my own laptop). Plugin updates and upgrades can be more safely quality tested and approved for upgrade in production. "Jenkins State Machine" When it comes to configuration management and an existing Jenkins installation I've always thought of what I call a "Jenkins State Machine". The Jenkins State Machine is essentially the following: If Jenkins is not in shutdown mode, then configuration changes can occur in the Jenkins runtime. If Jenkins is in shutdown mode, then don't make any configuration changes to Jenkins. i.e. any script which can change the runtime configuration should choose not to change if Jenkins is in this state. If Jenkins is in shutdown mode and there are jobs running, then Jenkins should not be restarted. A "restart" configuration management script should always just choose to wait to allow running jobs to finish. If Jenkins is in shutdown and there are no jobs running, then it is safe to restart Jenkins. The above state machine can be relatively safely run, automatically, without affecting users too drastically. Something like this can be done without much human intervention as long as the state machine is adhered in all config management scripts. The above state machine still poses minor problems. Any time jobs queue up during shutdown mode, the state of the queue is discarded on restart. The Jenkins job queue could be preserved when Jenkins is gracefully restarted or gracefully shut down. Configure via Script Console One of the most powerful things I've learned about Jenkins and the Script Console is that its runtime is itself the configuration. By updating the runtime, you're updating the configuration and can serialize that configuration to disk with a Jenkins.instance.save()
[JIRA] (JENKINS-36838) Generalize the notion of Steps taking over FlowNode creation
Title: Message Title Andrew Bayer commented on JENKINS-36838 Re: Generalize the notion of Steps taking over FlowNode creation With JENKINS-37011, I think we can be fine without this, but an example of what I want to be able to do is something like the matrix step I've mentioned before - syntactic sugar on top of parallel and withEnv in combination. 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-36838) Generalize the notion of Steps taking over FlowNode creation
Title: Message Title Jesse Glick commented on JENKINS-36838 Re: Generalize the notion of Steps taking over FlowNode creation Concrete use 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-36838) Generalize the notion of Steps taking over FlowNode creation
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-36838 Generalize the notion of Steps taking over FlowNode creation Change By: Jesse Glick Assignee: Andrew Bayer 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-36838) Generalize the notion of Steps taking over FlowNode creation
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36838 Generalize the notion of Steps taking over FlowNode creation Change By: Jesse Glick Labels: api 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-37190) Unauthenticated request to GitHub trigger rate limits when adding organization
Title: Message Title Giovanni Tirloni created an issue Jenkins / JENKINS-37190 Unauthenticated request to GitHub trigger rate limits when adding organization Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: github-api-plugin, github-organization-folder-plugin Created: 2016/Aug/04 8:57 PM Environment: Jenkins 2.16 GitHub API Plugin 1.76 GitHub Branch Source Plugin 1.8.1 GitHub Organization Folder Plugin 1.4 GitHub plugin 1.20.0 Pipeline 2.2 Priority: Minor Reporter: Giovanni Tirloni When adding a new GitHub organization, the initial attempts to create access it and create the GH webhooks do not seem to be authenticated, triggering GH's rate limits. Aug 04, 2016 8:45:10 PM org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl maybeApply WARNING: Failed to apply GitHub Org Folder theme to crash-test-dummies org.jenkinsci.plugins.github_branch_source.RateLimitExceededException: GitHub API rate limit exceeded at org.jenkinsci.plugins.github_branch_source.Connector$1.onError(Connector.java:177) at org.kohsuke.github.Requester.handleApiError(Requester.java:544) at org.kohsuke.github.Requester._to(Requester.java:264) at org.kohsuke.github.Requester.to(Requester.java:205) at org.kohsuke.github.GitHub.getUser(GitHub.java:293) at org.jenkinsci.plugins.orgfolder.github.MainLogic.applyOrg(MainLogic.java:62) at org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl.maybeApply(ItemListenerImpl.java:41) at org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl.onCreated(ItemListenerImpl.java:34) at hudson.model.listeners.ItemListener$2.apply(ItemListener.java:186) at
[JIRA] (JENKINS-32984) Reload Configuration from disk disrupts build elements and pipeline
Title: Message Title Jesse Glick commented on JENKINS-32984 Re: Reload Configuration from disk disrupts build elements and pipeline Reload Configuration from Disk has always been pretty buggy; it is best to avoid it when at all possible. You can always reload individual jobs, which is somewhat safer. 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-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Title: Message Title
Giovanni Tirloni edited a comment on JENKINS-34612
Re: Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Same issue encountered on the following environment:Jenkins 2.16GitHub API Plugin 1.76GitHub Branch Source Plugin 1.8.1GitHub Organization Folder Plugin 1.4GitHub plugin 1.20.0Pipeline 2.2 Steps to reproduce:1 - New Item2 - Enter GitHub organization name3 - Select "GitHub organization"4 - Click OKDetails:1 - Issue happens with and without a GitHub server added to Jenkins with the proper credentials.2 - Making user an owner or admin of the GH organization does not help. Stack trace:{noformat}Aug 04, 2016 8:14:26 PM WARNING org.jenkinsci.plugins.orgfolder.github.MainLogic applyOrgFailed to register GitHub Org hook to https://github.com/crash-test-dummies (missing permissions?): {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}Aug 04, 2016 8:14:26 PM FINE org.jenkinsci.plugins.orgfolder.github.MainLogicnulljava.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"} at org.kohsuke.github.Requester.handleApiError(Requester.java:553) at org.kohsuke.github.Requester._to(Requester.java:264) at org.kohsuke.github.Requester.to(Requester.java:205) at org.kohsuke.github.GHHooks$Context.getHooks(GHHooks.java:25) at org.kohsuke.github.GHOrganization.getHooks(GHOrganization.java:276) at org.jenkinsci.plugins.orgfolder.github.MainLogic.existsHook(MainLogic.java:198) at org.jenkinsci.plugins.orgfolder.github.MainLogic.applyOrg(MainLogic.java:89) at org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl.maybeApply(ItemListenerImpl.java:41) at org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl.onUpdated(ItemListenerImpl.java:29) at hudson.model.listeners.ItemListener$3.apply(ItemListener.java:195) at hudson.model.listeners.ItemListener$3.apply(ItemListener.java:193) at hudson.model.listeners.ItemListener.forAll(ItemListener.java:167) at hudson.model.listeners.ItemListener.fireOnUpdated(ItemListener.java:193) at com.cloudbees.hudson.plugins.folder.AbstractFolder.save(AbstractFolder.java:667) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList._onModified(PersistedList.java:181) at hudson.util.PersistedList.add(PersistedList.java:72) at jenkins.branch.CustomOrganizationFolderDescriptor.newInstance(CustomOrganizationFolderDescriptor.java:109) at hudson.model.ItemGroupMixIn.createProject(ItemGroupMixIn.java:323) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:203) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:3669) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 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
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Cody Scott commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. It looks like development has moved to https://github.com/jmdns/jmdns with the latest version being 3.5.1 https://github.com/jmdns/jmdns/releases 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-37187) Spot instances are counted twice towards cap
Title: Message Title Francis Upton closed an issue as Fixed Jenkins / JENKINS-37187 Spot instances are counted twice towards cap Change By: Francis Upton 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-37187) Spot instances are counted twice towards cap
Title: Message Title Francis Upton resolved as Fixed Jenkins / JENKINS-37187 Spot instances are counted twice towards cap Change By: Francis Upton 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-37187) Spot instances are counted twice towards cap
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37187 Re: Spot instances are counted twice towards cap Code changed in jenkins User: lsmith62 Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java http://jenkins-ci.org/commit/ec2-plugin/b3066e6033ecf66fc6a711225ba52d6c961f778c Log: JENKINS-37187 Avoid double counting spot instances 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-27079) ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title Craig Rodrigues resolved as Cannot Reproduce Cannot reproduce: Jenkins 2.16, multiple-scms 0.6, Subversion Plug-in 2.6 Jenkins / JENKINS-27079 ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState Change By: Craig Rodrigues Status: Reopened Resolved Resolution: Cannot Reproduce 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-37189) a file:// update center will always be offline
Title: Message Title
James Nord created an issue
Jenkins / JENKINS-37189
a file:// update center will always be offline
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Aug/04 8:20 PM
Environment:
windows
Priority:
Major
Reporter:
James Nord
The code in hudson.model.UpdateCenter$UpdateCenterConfiguration.checkUpdateCentermakes blind assumptions about the protocol and validity of an update center URL. Blindly appending a string to a URL does not necessarily a valid URL for connection checking make. For example the URL could be a file based url and the URL file://c:/some/path/to/updates.json will become file://c:/some/path/to/updates.json?uctest Later on the URL is used in hudson.model.UpdateCenter.UpdateCenterConfiguration.test connection(URL) - and if it is not a http URL it will try Util.copyStreamAndClose(connection.getInputStream(),new NullOutputStream()); which on windows will fail as it will try and open c:\some\path\to\updates.json?uctest which will fail with an exception - and then fail the update check.
public void checkUpdateCenter(ConnectionCheckJob job, String updateCenterUrl) throws IOException {
testConnection(new URL(updateCenterUrl + "?uctest"));
}
[JIRA] (JENKINS-34612) Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Title: Message Title
Giovanni Tirloni commented on JENKINS-34612
Re: Jenkins 2.1 not registering GitHub org webhooks: "WARNING: Failed to register GitHub Org hook to ..."
Same issue encountered on the following environment: Jenkins 2.16 GitHub API Plugin 1.76 GitHub Branch Source Plugin 1.8.1 GitHub Organization Folder Plugin 1.4 GitHub plugin 1.20.0 Pipeline 2.2 Stack trace:
Aug 04, 2016 8:14:26 PM WARNING org.jenkinsci.plugins.orgfolder.github.MainLogic applyOrg
Failed to register GitHub Org hook to https://github.com/crash-test-dummies (missing permissions?): {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
Aug 04, 2016 8:14:26 PM FINE org.jenkinsci.plugins.orgfolder.github.MainLogic
null
java.io.FileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
at org.kohsuke.github.Requester.handleApiError(Requester.java:553)
at org.kohsuke.github.Requester._to(Requester.java:264)
at org.kohsuke.github.Requester.to(Requester.java:205)
at org.kohsuke.github.GHHooks$Context.getHooks(GHHooks.java:25)
at org.kohsuke.github.GHOrganization.getHooks(GHOrganization.java:276)
at org.jenkinsci.plugins.orgfolder.github.MainLogic.existsHook(MainLogic.java:198)
at org.jenkinsci.plugins.orgfolder.github.MainLogic.applyOrg(MainLogic.java:89)
at org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl.maybeApply(ItemListenerImpl.java:41)
at org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl.onUpdated(ItemListenerImpl.java:29)
at hudson.model.listeners.ItemListener$3.apply(ItemListener.java:195)
at hudson.model.listeners.ItemListener$3.apply(ItemListener.java:193)
at hudson.model.listeners.ItemListener.forAll(ItemListener.java:167)
at hudson.model.listeners.ItemListener.fireOnUpdated(ItemListener.java:193)
at com.cloudbees.hudson.plugins.folder.AbstractFolder.save(AbstractFolder.java:667)
at hudson.util.PersistedList.onModified(PersistedList.java:173)
at hudson.util.PersistedList._onModified(PersistedList.java:181)
at hudson.util.PersistedList.add(PersistedList.java:72)
at jenkins.branch.CustomOrganizationFolderDescriptor.newInstance(CustomOrganizationFolderDescriptor.java:109)
at hudson.model.ItemGroupMixIn.createProject(ItemGroupMixIn.java:323)
at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:203)
at jenkins.model.Jenkins.doCreateItem(Jenkins.java:3669)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324)
at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52)
at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
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
[JIRA] (JENKINS-26734) Subversion Plugin 2.5 is incompatible with Multiple SCM plugin
Title: Message Title Craig Rodrigues resolved as Cannot Reproduce Cannot reproduce: Jenkins 2.16, multiple-scms 0.6, Subversion Plug-in 2.6 Jenkins / JENKINS-26734 Subversion Plugin 2.5 is incompatible with Multiple SCM plugin Change By: Craig Rodrigues Status: Reopened Resolved Resolution: Cannot Reproduce 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-26303) Not compatible with Subversion plugin 2.5
Title: Message Title Craig Rodrigues resolved as Cannot Reproduce Cannot reproduce: Jenkins 2.16, multiple-scms 0.6, Subversion Plug-in 2.6 Jenkins / JENKINS-26303 Not compatible with Subversion plugin 2.5 Change By: Craig Rodrigues Status: Reopened Resolved Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-37187) Spot instances are counted twice towards cap
Title: Message Title Leonard Smith updated an issue Jenkins / JENKINS-37187 Spot instances are counted twice towards cap Change By: Leonard Smith From testing on the latest version (1.35), it appears the spot instances end up being counted twice towards the instance cap. First, the instances themselves are counted (once the appropriate tag has been migrated from the spot request) and then the spot instance request itself is counted.If the plugin is responding to sudden demand, the cap seems to work fine since the SIRs are created before the tags make it to any instances. But, if you're at a steady state with the max number of SIRs, then terminating one of the requests will still leave you over the cap. See PR here: https://github.com/jenkinsci/ec2-plugin/pull/211 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
[JIRA] (JENKINS-27008) hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException
Title: Message Title Quentin Dufour edited a comment on JENKINS-27008 Re: hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException If you find this I've found issue during a while searching this error on Google Search .As this issue is referenced in search engines , I'm updating it .It might be because you're trying to run a very old Jenkins version with Java 8.I had this error while editing the git-client-plugin, which use Jenkins 1.532.2.I switched from JDK 1.8 to JDK 1.7 in Netbeans, and the error was fixed. But keep in mind that, indeed a stack trace is not enough. It could be an other error. Hope it will be useful to someone... 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-27008) hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException
Title: Message Title Quentin Dufour commented on JENKINS-27008 Re: hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException If you find this issue during a Google Search, it might be because you're trying to run a very old Jenkins version with Java 8. I had this error while editing the git-client-plugin, which use Jenkins 1.532.2. I switched from JDK 1.8 to JDK 1.7 in Netbeans, and the error was fixed. Hope it will be useful to someone... 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-37188) 2nd failure emails being sent even when build is successful
Title: Message Title Marc Esher created an issue Jenkins / JENKINS-37188 2nd failure emails being sent even when build is successful Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2016/Aug/04 7:29 PM Environment: Jenkins 2+, running on linux Priority: Minor Reporter: Marc Esher I have just configured some jobs to send emails on "Failure - 2nd" and "Fixed". The behavior I'm seeing is that if the job has ever failed in the past, then the "Failure - 2nd" email gets sent on every subsequent build, even if the build is successful. Here's the output I see in Jenkins: Email was triggered for: Failure - 2nd Trigger Failure - Any was overridden by another trigger and will not send an email. Trigger Failure - Still was overridden by another trigger and will not send an email. Sending email for trigger: Failure - 2nd Sending email to: .. Finished: SUCCESS The expected behavior, according to the plugin doc, is that it would only be sent on successive failures. Note that this build is neither a failure, nor a successive failure.
[JIRA] (JENKINS-34650) Allow global libraries to bypass the sandbox
Title: Message Title Jesse Glick updated JENKINS-34650 Jenkins / JENKINS-34650 Allow global libraries to bypass the sandbox Change By: Jesse Glick Status: In Review 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-34650) Allow global libraries to bypass the sandbox
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34650 Re: Allow global libraries to bypass the sandbox Code changed in jenkins User: Jesse Glick Path: doc/classloader.md pom.xml src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition.java src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.java src/main/java/org/jenkinsci/plugins/workflow/cps/CpsGroovyShellFactory.java src/main/java/org/jenkinsci/plugins/workflow/cps/GroovyClassLoaderWhitelist.java src/main/java/org/jenkinsci/plugins/workflow/cps/GroovyShellDecorator.java src/main/java/org/jenkinsci/plugins/workflow/cps/SandboxContinuable.java src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecutionTest.java src/test/resources/trusted/foo.groovy http://jenkins-ci.org/commit/workflow-cps-plugin/3a380e7b6905007f3612b57f67d1a2dcd67b9614 Log: Merge pull request #33 from jenkinsci/trusted-classloader JENKINS-34650 Added a trusted classloader that runs CPS code outside sandbox Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/da3757932771...3a380e7b6905 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-31155) Workflow shared library improvements
Title: Message Title Jesse Glick commented on JENKINS-31155 Re: Workflow shared library improvements Would be desirable to retain the benefit of JENKINS-34650 in some cases: for externally versioned libraries which we can say are “blessed” by a Jenkins administrator somehow, skip sandbox checks. But we also need regular developers to be able to define and use libraries, hence the need for an analogue of JENKINS-26538 (which might itself simply be closed, if this plan works out). 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-37187) Spot instances are counted twice towards cap
Title: Message Title Leonard Smith created an issue Jenkins / JENKINS-37187 Spot instances are counted twice towards cap Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Aug/04 7:25 PM Priority: Major Reporter: Leonard Smith From testing on the latest version (1.35), it appears the spot instances end up being counted twice towards the instance cap. First, the instances themselves are counted (once the appropriate tag has been migrated from the spot request) and then the spot instance request itself is counted. If the plugin is responding to sudden demand, the cap seems to work fine since the SIRs are created before the tags make it to any instances. But, if you're at a steady state with the max number of SIRs, then terminating one of the requests will still leave you over the cap. Add Comment
[JIRA] (JENKINS-37140) JNLP3-connect protocol format does not handle encrypted cookies that happen to contain a newline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37140 Re: JNLP3-connect protocol format does not handle encrypted cookies that happen to contain a newline Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/remoting/engine/JnlpServer3Handshake.java http://jenkins-ci.org/commit/remoting/7fbd009ddfb9a2944e27907f2f687030acdecb9d Log: Merge pull request #95 from jenkinsci/jenkins-37140 [FIXED JENKINS-37140] Roll the dice again if we are unlucky Compare: https://github.com/jenkinsci/remoting/compare/fe2feffc943b...7fbd009ddfb9 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-33114) Multibranch project should provide separate SCM source instead of using Branch source
Title: Message Title Rick Liu commented on JENKINS-33114 Re: Multibranch project should provide separate SCM source instead of using Branch source How about instead of providing a separate SCM source, could your provide an ENABLE/DISABLE configuration at Multibranch project level to control whether enable/disable the branch job SCM? Right now, on my local branch, I hard-coded to always disable the SCM for the branch job on Line 145 in File multibranch/TemplateDrivenBranchProjectFactory.java: https://github.com/totoroliu/multi-branch-project-plugin/commit/8737e3b250c5ab5ae3d3b45e65958b226a1609ae I just haven't figured out how to expose the Configuration UI at Multibranch-Pojrect Configuration using Jelly. 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-37186) Jar is missing classes
Title: Message Title Stuart Finley created an issue Jenkins / JENKINS-37186 Jar is missing classes Issue Type: Bug Assignee: uzilan Attachments: JenkinsJar.png, LocalJar.png Components: sbt-plugin Created: 2016/Aug/04 7:07 PM Environment: 1.625.16.1 (CloudBees Jenkins Enterprise 15.11) running on Windows Server 2012 with two slaves doing the builds Labels: plugin jenkins sbt Priority: Blocker Reporter: Stuart Finley We get "successful" builds using the SBT Plugin, but the fat .jar file is missing almost all dependencies. The log looks correct compared to a local build in Intellij. The size of the .jar is close to a correct build, but obviously the checksum is wrong. Partial log: [Deploy ContentSeasonalityScoring to Test] $ cmd.exe /C " java -Dsbt.log.noformat=true -jar d:\Jenk\tools\org.jvnet.hudson.plugins.SbtPluginBuilder_SbtInstallation\SBT_0.13.11\bin\sbt-launch.jar clean " [info] Loading project definition from D:\Jenk\workspace\MarketingData\Deploy ContentSeasonalityScoring to Test\project [info] Set current project to ContentSeasonalityScoring (in build file:/D:/Jenk/workspace/MarketingData/Deploy%20ContentSeasonalityScoring%20to%20Test/) [success] Total time: 16 s, completed Aug 4, 2016 7:00:44 AM Build step 'Build using sbt' changed build result to SUCCESS [Deploy ContentSeasonalityScoring to Test] $ cmd.exe /C " java -Dsbt.log.noformat=true -jar
[JIRA] (JENKINS-30183) Openstack Cloud Plugin does not wait until the user data script completes
Title: Message Title Joshua Harlow commented on JENKINS-30183 Re: Openstack Cloud Plugin does not wait until the user data script completes Do u know what image u were trying this on, a image with systemd? Knowing that will help me figure out how to adjust the module order in cloud-init to better suit what u want to do. 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-37184) Exception about tunnel goes unreported, svn-list-tags lists top level folder instead of branches and tags
Title: Message Title Manuel Recena Soto started work on JENKINS-37184 Change By: Manuel Recena Soto 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-37184) Exception about tunnel goes unreported, svn-list-tags lists top level folder instead of branches and tags
Title: Message Title Manuel Recena Soto assigned an issue to Brian DeRocher Jenkins / JENKINS-37184 Exception about tunnel goes unreported, svn-list-tags lists top level folder instead of branches and tags Change By: Manuel Recena Soto Assignee: Brian DeRocher 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-36623) Test failing against Jenkins 1.651.3
Title: Message Title
Manuel Recena Soto updated an issue
Jenkins / JENKINS-36623
Test failing against Jenkins 1.651.3
Change By:
Manuel Recena Soto
* h4. Description :* Four tests are failing for different reasons.* hudson.plugins.promoted_builds.conditions.inheritance.SelfPromotionInheritanceTest.testPromotionEnvironmentShouldIncludeTargetParameters is failing because of SECURITY-170* The rest of tests are failing because they are not compatible with Jenkins baseline 1.575+. See [here|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/test/java/hudson/plugins/promoted_builds/PromotionProcessTest.java#L56] * h4. How to reproduce :* * Compile the test{noformat}mvn clean compile test-compile{noformat}* Execute the tests against the last LTS{noformat}mvn test -Djenkins.version=1.651.3{noformat}
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
[JIRA] (JENKINS-33114) Multibranch project should provide separate SCM source instead of using Branch source
Title: Message Title Jesse Glick resolved as Won't Do I want to use different SCM or even manually handle SCM in SHELL or GROOVY script This is exactly what multibranch Pipeline projects let you do. This issue sounds like a mixture of different use cases, some already satisfiable. Jenkins / JENKINS-33114 Multibranch project should provide separate SCM source instead of using Branch source Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36896) Stack Trace on startup
Title: Message Title
Frank Racis commented on JENKINS-36896
Re: Stack Trace on startup
Here's a diff that will just log a warning instead of completely failing the startup:
diff --git a/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/TemplateDrivenMultiBranchProject.java b/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/TemplateDrivenMultiBranchProject.java
index c52dceb..8cb30d4 100644
--- a/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/TemplateDrivenMultiBranchProject.java
+++ b/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/TemplateDrivenMultiBranchProject.java
@@ -714,7 +714,8 @@ public abstract class TemplateDrivenMultiBranchProjectextends AbstractProject
File[] contents = dir.listFiles();
if (null == contents) {
-throw new IOException("Tried to treat '" + dir + "' as a directory, but could not get a listing");
+LOGGER.log(Level.WARNING, "Tried to treat '" + dir + "' as a directory, but could not get a listing");
+return files;
}
for (final File file : contents) {
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
[JIRA] (JENKINS-34725) Multibranch Plugin: Shouldn't run every branch on re-index
Title: Message Title Jesse Glick resolved as Won't Do See above. Jenkins / JENKINS-34725 Multibranch Plugin: Shouldn't run every branch on re-index Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do 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-24614) "unknown format type" on console output
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24614 Re: "unknown format type" on console output Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/Run/console_he.properties http://jenkins-ci.org/commit/jenkins/a452e2d72124def43e57b2cc78e2e3768bc85186 Log: [FIXED JENKINS-24614] Broken format string in Hebrew console output (cherry picked from commit 07fd5fa45d4b818fc11de97ce99ab6b3423aca85) 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-23471) Channel reader thread consumes all CPUs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-23471 Re: Channel reader thread consumes all CPUs Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/91c5551d4c7682d4adba28fe591fa7772eee62e0 Log: [JENKINS-23471 JENKINS-24050] Integrated the fix in remoting to Jenkins 1.580. (cherry picked from commit 8fc609fe0952b285d5b26a59fd5ff4c29704d33d) 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-24458) doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24458 Re: doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/12a4b444a96d30a57e78c2427d07a46172aeb8e8 Log: [JENKINS-24458 JENKINS-11543] integrated the newer version of stapler with reduced log level (cherry picked from commit c57f9ed577b9635f01aa5affabf1f770b689a115) Conflicts: changelog.html 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-27120) Make JacocoPublisher a SimpleBuildStep
Title: Message Title Brian St.Clair commented on JENKINS-27120 Re: Make JacocoPublisher a SimpleBuildStep I just found this PR: https://github.com/jenkinsci/jacoco-plugin/pull/66 but I don't see the commit in master? 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-11543) UTF-8 encoding issue of build parameters as soon as including File parameter
Title: Message Title SCM/JIRA link daemon commented on JENKINS-11543 Re: UTF-8 encoding issue of build parameters as soon as including File parameter Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/12a4b444a96d30a57e78c2427d07a46172aeb8e8 Log: [JENKINS-24458 JENKINS-11543] integrated the newer version of stapler with reduced log level (cherry picked from commit c57f9ed577b9635f01aa5affabf1f770b689a115) Conflicts: changelog.html 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-24050) All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24050 Re: All slaves disconnect and no new slaves can connect due to CancelledKeyException in org.jenkinsci.remoting Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html pom.xml http://jenkins-ci.org/commit/jenkins/91c5551d4c7682d4adba28fe591fa7772eee62e0 Log: [JENKINS-23471 JENKINS-24050] Integrated the fix in remoting to Jenkins 1.580. (cherry picked from commit 8fc609fe0952b285d5b26a59fd5ff4c29704d33d) 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-37179) Unable to scroll down/up jobs in view, in case if job doesn't fit to area
Title: Message Title Andrey Shevtsov commented on JENKINS-37179 Re: Unable to scroll down/up jobs in view, in case if job doesn't fit to area Try playing with height ratio and button size in settings. To get to the settings page, click the cogwheel icon in the top-right corner. Let me know if that works for you. 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-30828) Keep history of jobs config changes when they are moved across folders
Title: Message Title Kalle Sirkesalo commented on JENKINS-30828 Re: Keep history of jobs config changes when they are moved across folders Easiest way would be to track the movement and then just move the old files with the job. It shouldn't be too bad at least when you move stuff inside a folder. 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-27120) Make JacocoPublisher a SimpleBuildStep
Title: Message Title Brian St.Clair commented on JENKINS-27120 Re: Make JacocoPublisher a SimpleBuildStep I'd like to get this update. I looked through the GitHub repo here https://github.com/jenkinsci/jacoco-plugin. Is that the right repo? Apologies, but I can't find the commit/label/release to pull that includes this change. Is it in there somewhere? 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-37125) ability to write and use groovy classes from pipeline repos / scripts
Title: Message Title
Chris Price commented on JENKINS-37125
Re: ability to write and use groovy classes from pipeline repos / scripts
jglick, in IRC, pointed me at GroovyShellDecorator. I can imagine adding a GroovyShellDecorator to the plugin, and having it check for a file like {{$ {workspace} /.jenkins/additional_classpath_entries}} and if it finds it, read lines from the file and add them to the classpath for the GroovyShell. However, jglick warned that this won't work for jobs that are running on jenkins nodes other than the master because their workspaces will be remote :/
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-36757) incorrect logging formats in setup wizard.
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-36757 incorrect logging formats in setup wizard. Change By: James Nord Assignee: James Nord 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-36757) incorrect logging formats in setup wizard.
Title: Message Title James Nord started work on JENKINS-36757 Change By: James Nord 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-37185) Checkout timeout is not honored when used with local branch parameter
Title: Message Title Quentin Dufour updated an issue Jenkins / JENKINS-37185 Checkout timeout is not honored when used with local branch parameter Change By: Quentin Dufour *Expectation:* When I set the checkout timeout, I'm expecting that Jenkins uses it when it comes to checkout a commit.*Problem:* However, it appears that when you select the "Check out to a specific local branch", the first checkout command does not set correctly the timeout.*Why it's a problem:* I'm using git lfs, and git lfs files are downloaded during the checkout option. For other reasons I can't use the git lfs pull command. Especially during the first checkout command.*How to reproduce it:* Use any version of git-plugin and git-client-plugin. Create a freestyle project, add the following parameters: Timeout=120 for Advanced checkout option, and Checkout to a specific local branch. Build the project. The first checkout will be displayed with a timeout of 10 instead of 120. _I've a Here is my proposition to fix this error: https://github . Not yet linked because I need the JIRA id before_ com/jenkinsci/git-client-plugin/pull/214 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36757) incorrect logging formats in setup wizard.
Title: Message Title James Nord commented on JENKINS-36757 Re: incorrect logging formats in setup wizard. to use a single quote ' in a message format you must use double single quotes '' 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-37185) Checkout timeout is not honored when used with local branch parameter
Title: Message Title Quentin Dufour created an issue Jenkins / JENKINS-37185 Checkout timeout is not honored when used with local branch parameter Issue Type: Bug Assignee: Quentin Dufour Components: git-client-plugin Created: 2016/Aug/04 5:33 PM Priority: Minor Reporter: Quentin Dufour Expectation: When I set the checkout timeout, I'm expecting that Jenkins uses it when it comes to checkout a commit. Problem: However, it appears that when you select the "Check out to a specific local branch", the first checkout command does not set correctly the timeout. Why it's a problem: I'm using git lfs, and git lfs files are downloaded during the checkout option. For other reasons I can't use the git lfs pull command. Especially during the first checkout command. How to reproduce it: Use any version of git-plugin and git-client-plugin. Create a freestyle project, add the following parameters: Timeout=120 for Advanced checkout option, and Checkout to a specific local branch. Build the project. The first checkout will be displayed with a timeout of 10 instead of 120. I've a fix. Not yet linked because I need the JIRA id before Add Comment
[JIRA] (JENKINS-32767) GitSCMSource can hang in branch indexing, blocking builds
Title: Message Title Mark Waite commented on JENKINS-32767 Re: GitSCMSource can hang in branch indexing, blocking builds Pull request 424 allows AbstractGitSCMSource to use command line git. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33846) Restart pipeline from specific stage, after failure
Title: Message Title Noah Nordrum commented on JENKINS-33846 Re: Restart pipeline from specific stage, after failure Michael Hüttermann Jean-Marc Collin Seems like there's an opportunity to create an OSS plugin that does this. Tweet me if you guys want to work together to make one. Noah 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-37184) Exception about tunnel goes unreported, svn-list-tags lists top level folder instead of branches and tags
Title: Message Title Brian DeRocher commented on JENKINS-37184 Re: Exception about tunnel goes unreported, svn-list-tags lists top level folder instead of branches and tags https://github.com/jenkinsci/subversion-plugin/pull/165 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-5124) svn-tag doesn't understand [tunnels]
Title: Message Title Brian DeRocher commented on JENKINS-5124 Re: svn-tag doesn't understand [tunnels] Is fixed by this PR https://github.com/jenkinsci/subversion-plugin/pull/165 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-37184) Exception about tunnel goes unreported, svn-list-tags lists top level folder instead of branches and tags
Title: Message Title Brian DeRocher commented on JENKINS-37184 Re: Exception about tunnel goes unreported, svn-list-tags lists top level folder instead of branches and tags I have a fix for this bug and will submit a PR on github. 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-37011) Provide a way to write full-fledged Steps in CPS-transformed Groovy
Title: Message Title Jesse Glick started work on JENKINS-37011 Change By: Jesse Glick 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.
