[JIRA] (JENKINS-54956) Github merge refs not working correctly
Title: Message Title
Liam Newman edited a comment on JENKINS-54956
Re: Github merge refs not working correctly
[~thomas_deepomatic], [~jraezrus]4h is particularly long. That email if very confusing. I guess it is technically true, 'refs/pulls//merge' is not specifically documented, but multiple things related to it are.{{Merge_commit_sha}} and {{refs/pulls//head}} are directly connected to this and have documentation. https://developer.github.com/v3/pulls/#get-a-single-pull-request (see response). Could you try out github branch source plugin v2.5.1. This may address this issue for you - or it may make the situation works more extreme deeply but also in a more accurate way with these APIs . If nothing else, it would be very useful to have more data from the current version of the plugin.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54956) Github merge refs not working correctly
Title: Message Title Liam Newman commented on JENKINS-54956 Re: Github merge refs not working correctly Thomas Riccardi, Javier Raez 4h is particularly long. That email if very confusing. I guess it is technically true, 'refs/pulls//merge' is not specifically documented, but multiple things related to it are. Merge_commit_sha and refs/pulls//head are directly connected to this and have documentation. https://developer.github.com/v3/pulls/#get-a-single-pull-request (see response). Could you try out github branch source plugin v2.5.1. This may address this issue for you - or it may make the situation more extreme. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57279) Github Organization PRs not building on agents
Title: Message Title Jorge Guzman commented on JENKINS-57279 Re: Github Organization PRs not building on agents Thanks Liam! I will try this and get back to you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54956) Github merge refs not working correctly
Title: Message Title Liam Newman started work on JENKINS-54956 Change By: Liam Newman Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57303) Duplicate builds triggered from webhook (push) on branch pipelines
Title: Message Title Liam Newman commented on JENKINS-57303 Re: Duplicate builds triggered from webhook (push) on branch pipelines It looks like this is duplicate of JENKINS-54610. Does that look right to you? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54495) Better handling of GitHub Organization folder scan to avoid API quota
Title: Message Title Liam Newman commented on JENKINS-54495 Re: Better handling of GitHub Organization folder scan to avoid API quota Any of these seems like interesting options. Targeted scan - This would involve some working with Jelly and Jenkins UI, but it might be easier to implement due to the narrow target. Shallow scan - At very least, doing a breadth first scan that then requested scans from the child repo's over time. The GraphQL option would be a massive undertaking. But maybe if you switched just to top level repo scan or some other targeted scenario. They're all viable in different ways. Perhaps you could file a separate issue for each one and then work on them separately? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54265) Sending Parameters or initialize environment variables
Title: Message Title Liam Newman commented on JENKINS-54265 Re: Sending Parameters or initialize environment variables Are you talking about the JobDSL plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57195) Scan organization fails with FileNotFoundException
Title: Message Title Liam Newman commented on JENKINS-57195 Re: Scan organization fails with FileNotFoundException This sound like some kind of condition where permissions haven't caught up with your settings. Do you get it each time you create a new private repo? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57279) Github Organization PRs not building on agents
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-57279 Github Organization PRs not building on agents Change By: Liam Newman Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57279) Github Organization PRs not building on agents
Title: Message Title Liam Newman commented on JENKINS-57279 Re: Github Organization PRs not building on agents Okay, even in that state some things still run on master - parts of pipeline are controlled from Jenkins master and run in what is called a "flyweight" executor. These can't be disabled, but they should only be minimal control threads. Before Github Branch Source 2.5.x, this meant that for Merge PRs we'd also clone on master to get the merged Jenkinsfile. Maybe that is what you're seeing executing. In 2.5.x, we've move to using the GitHub API for PRs. You might try testing out this new version and see if it addresses your problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Josh Soref In what context is this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Liam Newman started work on JENKINS-56996 Change By: Liam Newman Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Liam Newman updated JENKINS-56996 Jenkins / JENKINS-56996 null permission lookup when pull-request's origin repo/branch is deleted on github Change By: Liam Newman Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57319) HockeyApp Plugin "unexpected response code from HockeyApp: 400"
Title: Message Title Mez Pahlan commented on JENKINS-57319 Re: HockeyApp Plugin "unexpected response code from HockeyApp: 400" Hi Madhu A I've made a fix that I think might work for both types of project freestyle and pipeline. Would you mind testing 1.5.1 out before I merge it. You can find 1.5.1 on the CI server https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fhockeyapp-plugin/detail/PR-61/2/artifacts And the associated Github PR: https://github.com/jenkinsci/hockeyapp-plugin/pull/61 Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27165) Specify release_type
Title: Message Title Mez Pahlan closed an issue as Won't Fix Plugin to be sunset. Jenkins / JENKINS-27165 Specify release_type Change By: Mez Pahlan Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26018) HockeyApp plugin does not support DMG or PKG files
Title: Message Title Mez Pahlan closed an issue as Won't Fix Plugin to be sunset. Jenkins / JENKINS-26018 HockeyApp plugin does not support DMG or PKG files Change By: Mez Pahlan Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33189) When uploading multiple, don't error out if 1 fails
Title: Message Title Mez Pahlan closed an issue as Won't Fix Plugin to be sunset. Jenkins / JENKINS-33189 When uploading multiple, don't error out if 1 fails Change By: Mez Pahlan Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32855) Can not enter AppId and Release notes when setting up more than one app
Title: Message Title Mez Pahlan closed an issue as Won't Fix Plugin to be sunset. Jenkins / JENKINS-32855 Can not enter AppId and Release notes when setting up more than one app Change By: Mez Pahlan Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.
Title: Message Title Ondrej Burkert commented on JENKINS-39874 Re: Abilty to disable pipeline-replay in Job Configuration. Jesse Glick true, the fact that the person can configure the job allows them to do whatever already... Thanks for clarifying. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41037) Unabel to serialize mock because of ConcurrentModificationException
Title: Message Title Logan Highland commented on JENKINS-41037 Re: Unabel to serialize mock because of ConcurrentModificationException We ran into this issue on the first build of a branch pipeline job. Same exact stack trace as Bahram Parsapour ran into. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Robin Verduijn commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log Note that for me, I am also still seeing the control characters in the console output but only while watching an active build. Inspecting the console output after a build has completed does render them correctly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-8217) Extension settings aren't reloaded from XML files
Title: Message Title Ladislav Toldy commented on JENKINS-8217 Re: Extension settings aren't reloaded from XML files It would be nice if reload option can reload configuration from file system. Currently it does only for small percentage of config, definitely far from "everything". We deploy jenkins using ansible, configuring on filesystem level, if reload can include plugins as well it would be superuseful for us not to need to plan restart. Btw still happening in the 2.174 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Jesse Glick commented on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel In the Gatling plugin, apparently some state was needed in the action, though the full file path was surely overkill. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits
Title: Message Title Karl Shultz commented on JENKINS-23606 Re: Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits Tomasz M (and others) - here's a question about the issues you're experiencing with included and excluded regions. Are you, by chance, starting your included regions with a leading /, as lledhub dell alluded to in this comment from September 9, 2016? I've written eight new tests that look at included/excluded areas specifically with merge commits. It took me a really, really long time to see it, but eventually I realized that the last failing test was failing because it had committed directory/filename to the git repository, but the included/excluded region pattern was looking for /directory/filename. The difference was that leading slash. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23570) Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes
Title: Message Title David Westd commented on JENKINS-23570 Re: Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes So sad this is closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Jesse Glick commented on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel Prepared a core patch to make these errors nonfatal, and patches for the Maven and SCoverage plugins to not attempt to store FilePath instances. (In both cases, the object referred always to a local file on the Jenkins master, so a File or String would have sufficed; and no such field was actually needed to begin with. Same in JENKINS-57229 I think.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Jesse Glick updated JENKINS-57244 Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33430) Stage view UI loses history when stages are changed
Title: Message Title Jim Doyle commented on JENKINS-33430 Re: Stage view UI loses history when stages are changed I'd like to add my vote to this issue, but the option seems disabled - is it because this issue is marked "Resolved"? I'm not a contributor, and realize that there are often thorny details the user doesn't see, but it seems like there might be a big difference between solving the general form of the problem and just implementing a minimal use case (no cross-referencing, no renames, etc.) that achieves the main goal of visualizing old builds. I'm not sure it's really a new visualization combining all the history that's desirable. A user (I think) just wants to be able to see the same visualization they saw the day before, somewhere in the UI, even if it can't include the newer builds. In my mind, it's not even a prerequisite for all the sequences of builds to be on the same screen as long as you can find them somewhere. For instance, based on the mockup screen example, what if: If the user clicks on the project page "TestProject" it shows the same Stage View it would show today, with the recent builds #4, #5, #6 that have the same stages. If the user clicks the build page for #3, it would have a new link "Stage View History", which would open a display showing what the Stage View used to look like - build #3 with the old stages If the user clicks the build page for #1, it also would have "Stage View History", which would show the even-earlier Stage View - build #1 with just the two stages. Or to make it a better example, if there were a build #2 with the same stages as #3, the Stage View History for build #3 would show two builds #2 and #3, so that even though these two builds weren't with the current stages, you could see them shown together because they had the same stages. Don't the build logs have all the information the UI would need to do that? Wouldn't the current algorithm suffice, just pretending the older build is the latest build that it must count the stages from? Thanks! Add Comment
[JIRA] (JENKINS-34268) Lock multiple resources using the Pipeline lock step
Title: Message Title
Chris Dickinson commented on JENKINS-34268
Re: Lock multiple resources using the Pipeline lock step
Anyone hoping to make use of locking a dynamic list of resources will probably find this feature (if it was ever implemented) doesn't work in v2.4 of the plugin. So, I whipped up the following helper function which should allow you to do so:
def lockResources(listOfResources, closure) {
if (listOfResources.size() > 1) {
lockResources(listOfResources[1..-1], { lock(listOfResources[0]) { closure() }})
} else {
lock(listOfResources[0]) { closure() }
}
}
Example usage:
def resources = ['foo', 'bar', 'baz']
lockResources(myResources, {
print('hello, world')
})
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57247) how to enable access log when your jenkins master is running on redhat linux
Title: Message Title Mohit Saraf commented on JENKINS-57247 Re: how to enable access log when your jenkins master is running on redhat linux please suggest if anyone has implemented the same. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22945) Export git tag message as an environment variable
Title: Message Title Christopher Orr closed an issue as Won't Do I implemented this as a separate plugin: [https://github.com/jenkinsci/git-tag-message-plugin|Git Tag Message plugin]. Jenkins / JENKINS-22945 Export git tag message as an environment variable Change By: Christopher Orr Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22945) Export git tag message as an environment variable
Title: Message Title Christopher Orr edited a comment on JENKINS-22945 Re: Export git tag message as an environment variable I implemented this as a separate plugin: [ Git Tag Message| https://github.com/jenkinsci/git-tag-message-plugin |Git Tag Message plugin ]. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57279) Github Organization PRs not building on agents
Title: Message Title Jorge Guzman commented on JENKINS-57279 Re: Github Organization PRs not building on agents Thanks for helping out! Yes, master node has been configured with 0 executors and to build jobs only matching it. See attached pictures. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57279) Github Organization PRs not building on agents
Title: Message Title Jorge Guzman updated an issue Jenkins / JENKINS-57279 Github Organization PRs not building on agents Change By: Jorge Guzman Attachment: Screen Shot 2019-05-03 at 9.39.46 AM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Jose Valverde commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files Hi Karl Wirth . Thanks for you feedback, In the meanwhile, I'll try to sync my workspace as you've instructed! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57258) Lost builds historical data after updating to Jenkins v2.175
Title: Message Title Nicolas Echegut commented on JENKINS-57258 Re: Lost builds historical data after updating to Jenkins v2.175 I don't see anything useful in the log and error files from the day of the upgrade. I'm not using the SCoverage plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51577) Windows service wrapper for slave.jar can not connect to a SSL configured master
Title: Message Title Oleg Nenashev updated JENKINS-51577 Jenkins / JENKINS-51577 Windows service wrapper for slave.jar can not connect to a SSL configured master Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51577) Windows service wrapper for slave.jar can not connect to a SSL configured master
Title: Message Title Oleg Nenashev commented on JENKINS-51577 Re: Windows service wrapper for slave.jar can not connect to a SSL configured master https://github.com/jenkinsci/jenkins/pull/4010 is a PR against the core. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51577) Windows service wrapper for slave.jar can not connect to a SSL configured master
Title: Message Title Oleg Nenashev started work on JENKINS-51577 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title jeremy hochheiser commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 Sam Gleske and Mark Dietzer, this is still an issue all the way from 2.131.2 to LTS (2.164.2). We are stuck on 2.131.1 and unable to move forwards until this is resolved. Could you please revisit this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57211) Jenkins won't start due to some User Migration Exception.
Title: Message Title Jeff Thompson commented on JENKINS-57211 Re: Jenkins won't start due to some User Migration Exception. This sounds like the same thing discussed on the user email list at https://groups.google.com/d/msg/jenkinsci-users/h-Eku3NnWLg/le9Xx_a4CQAJ . In that case it did turn out to be connected to underlying filesystem problems. We saw a number of filesystem errors in the logs and other similar problems in other software. In that case, the user was able to run on a different system and avoid the problems entirely. If you can, try running the same upgrade on a different system with a more stable filesystem. Or reconfigure your environment to make the filesystem more stable. We would need lot more information about the environment and the logs before we could diagnose anything further. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42192) permissive-security-script plugin should not log full stacktrace
Title: Message Title
Prachi Khadke edited a comment on JENKINS-42192
Re: permissive-security-script plugin should not log full stacktrace
I am having the same problem as Alexander Komarov.{code:java}Scripts not permitted to use staticMethod org.jenkinsci.plugins.workflow.cps.Safepoint safepoint.Administrators can decide whether to approve or reject this signature.{code}I have approved the signature several times without any difference. My build still fails with the same error. Also tried setting{code:java}-Dpermissive-script-security.enabled=no_security{code}in the{code:java} /etc/sysconfig/jenkins{code}config file to no avail. But my point is the fact that the build failing with the error above despite approving the signature is a bug. I shouldn't have to disable permissive script security for my builds to run. And I should be able to select approve operations that I can explicitly allow to run within the sandbox.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42192) permissive-security-script plugin should not log full stacktrace
Title: Message Title
Prachi Khadke edited a comment on JENKINS-42192
Re: permissive-security-script plugin should not log full stacktrace
I am having the same problem as Alexander Komarov.{code:java}Scripts not permitted to use staticMethod org.jenkinsci.plugins.workflow.cps.Safepoint safepoint.Administrators can decide whether to approve or reject this signature.{code}I have approved the signature several times without any difference. My build still fails with the same error. Also tried setting{code:java}-Dpermissive-script-security.enabled=no_security{code}in the{code:java} /etc/sysconfig/jenkins{code}config file to no avail. But my point is the fact that the build failing with the error above despite approving the signature is a bug. I shouldn't have to disable permissive script security for my builds to run. And I should be able to select operations that I can explicitly allow to run within the sandbox.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42192) permissive-security-script plugin should not log full stacktrace
Title: Message Title
Prachi Khadke edited a comment on JENKINS-42192
Re: permissive-security-script plugin should not log full stacktrace
I am having the same problem as Alexander Komarov.{code:java}Scripts not permitted to use staticMethod org.jenkinsci.plugins.workflow.cps.Safepoint safepoint.Administrators can decide whether to approve or reject this signature.{code}I have approved the signature several times without any difference. My build still fails with the same error. Also tried setting{code:java}-Dpermissive-script-security.enabled=no_security{code}in the{code:java} /etc/sysconfig/jenkins{code}config file to no avail. But my point is the fact that the build failing with the error above despite approving the signature is a bug. I shouldn't have to disable permissive script security for my builds to run.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42192) permissive-security-script plugin should not log full stacktrace
Title: Message Title
Prachi Khadke edited a comment on JENKINS-42192
Re: permissive-security-script plugin should not log full stacktrace
I am having the same problem as Alexander Komarov.{code:java}Scripts not permitted to use staticMethod org.jenkinsci.plugins.workflow.cps.Safepoint safepoint.Administrators can decide whether to approve or reject this signature.{code} I have approved the signature several times without any difference. My build still fails with the same error. Also tried setting{code:java}-Dpermissive-script-security.enabled=no_security{code}in the{code:java} /etc/sysconfig/jenkins{code}config file to no avail. But my point is the fact that the build failing with the error above despite approving the signature is a bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42192) permissive-security-script plugin should not log full stacktrace
Title: Message Title
Prachi Khadke edited a comment on JENKINS-42192
Re: permissive-security-script plugin should not log full stacktrace
I am having the same problem as Alexander Komarov. {code:java} ` Scripts not permitted to use staticMethod org.jenkinsci.plugins.workflow.cps.Safepoint safepoint. [ Administrators can decide whether to approve or reject this signature. |https://jenkins-b2b.media.weather.com/scriptApproval]` {code} I have approved the signature several times without any difference. My build still fails with the same error. Also tried setting ` {code:java} -Dpermissive-script-security.enabled=no_security ` {code} in the ` {code:java} /etc/sysconfig/jenkins ` {code} config file to no avail. But my point is the fact that the build failing with the error above despite approving the signature is a bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42192) permissive-security-script plugin should not log full stacktrace
Title: Message Title Prachi Khadke commented on JENKINS-42192 Re: permissive-security-script plugin should not log full stacktrace I am having the same problem as Alexander Komarov. ` Scripts not permitted to use staticMethod org.jenkinsci.plugins.workflow.cps.Safepoint safepoint. Administrators can decide whether to approve or reject this signature.` I have approved the signature several times without any difference. My build still fails with the same error. Also tried setting `-Dpermissive-script-security.enabled=no_security` in the `/etc/sysconfig/jenkins` config file to no avail. But my point is the fact that the build failing with the error above despite approving the signature is a bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57325) Groovy Generator
Title: Message Title Tanja Roithmeier created an issue Jenkins / JENKINS-57325 Groovy Generator Issue Type: Improvement Assignee: Tanja Roithmeier Components: warnings-ng-plugin Created: 2019-05-03 15:07 Priority: Minor Reporter: Tanja Roithmeier Create a page object for the groovy generator at the configuration page. The page object should inherit from the configuration page object and should return generated configuration as String Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-57314 P4 Sync to label after sync to head without deleting non labeled files Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57314 P4 Sync to label after sync to head without deleting non labeled files Change By: Karl Wirth Labels: P4_B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Karl Wirth commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files Hi Jose Valverde. I have not been able to find a way to do this so will mark this as an enhancement request for the developers. The workaround would be to do the whole sync using P4Groovy: https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/p4groovy.html?Highlight=P4Groovy You could then specify the command line you need for the sync. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Jesse Glick commented on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel I think I understand the problem in the Maven plugin, but need to write a test to reproduce it—the existing test suite, though quite large, appears to never exercise the Javadoc reporter which is the source of the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57286) Trend Charts (in job summary view)
Title: Message Title Tanja Roithmeier assigned an issue to Unassigned Jenkins / JENKINS-57286 Trend Charts (in job summary view) Change By: Tanja Roithmeier Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57286) Trend Charts (in job summary view)
Title: Message Title Tanja Roithmeier assigned an issue to Ulli Hafner Jenkins / JENKINS-57286 Trend Charts (in job summary view) Change By: Tanja Roithmeier Assignee: Tanja Roithmeier Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title
Mario Jauvin updated an issue
Jenkins / JENKINS-57324
Error running maven with settings file when running multibranch pipeline with a slash in the branch
Change By:
Mario Jauvin
I configured a maven settings and global settings file in the Pipeline Maven Configuration of the folder containing the multibranch pipeline job. When I run the following stage from my Jenkins file:{quote}stage('Package') { steps { withMaven() { bat " set MAVEN& mvn ${env.MAVEN_VERBOSE} clean package ${env.RELEASE_VERSION_PARAMETERS}" }} }{quote}I get this error:{quote}[ERROR] Error executing Maven. [ERROR] The specified user settings file does not exist: C:\jenkins\dctl\branchespackageFspring-boot\workspace@tmp\withMaven22e2d518\settings.xml{quote}The reason I get this error is that the folder containing the branch is called branches%2Fspring-boot and the config file provider is replacing %2 with package (I assume this is the second argument to the script that is invoked)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Mario Jauvin updated an issue Jenkins / JENKINS-57324 Error running maven with settings file when running multibranch pipeline with a slash in the branch Change By: Mario Jauvin Labels: windows Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title
Mario Jauvin updated an issue
Jenkins / JENKINS-57324
Error running maven with settings file when running multibranch pipeline with a slash in the branch
Change By:
Mario Jauvin
I configured a maven settings and global settings file in the Pipeline Maven Configuration of the folder containing the multibranch pipeline job. When I run the following stage from my Jenkins file:{quote}stage('Package') { steps { withMaven() { bat "set MAVEN ${env.MAVEN_VERBOSE} clean package ${env.RELEASE_VERSION_PARAMETERS}" }} }{quote}I get this error:{quote}[ERROR] Error executing Maven. [ERROR] The specified user settings file does not exist: e C :\ cc-build jenkins \ checkout\aws\ dctl\branchespackageFspring-boot\workspace@tmp\withMaven22e2d518\settings.xml{quote} The reason I get this error is that the folder containing the branch is called branches%2Fspring-boot and the config file provider is replacing %2 with package (I assume this is the second argument to the script that is invoked)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Gabriel Lavoie edited a comment on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down [~ifernandezcalvo] any update about releasing a new version of the ssh-slaves plug plugin with this the latest trilead-ssh? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down
Title: Message Title Gabriel Lavoie commented on JENKINS-53468 Re: Since 1.27 update Channel is closing or has closed down Ivan Fernandez Calvo any update about releasing a new version of the ssh-slaves plug with this the latest trilead-ssh? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title
Mario Jauvin created an issue
Jenkins / JENKINS-57324
Error running maven with settings file when running multibranch pipeline with a slash in the branch
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
config-file-provider-plugin
Created:
2019-05-03 14:56
Environment:
Confile File Provider ver 3.6 Jenkins ver 2.164.2 Windows 10
Priority:
Major
Reporter:
Mario Jauvin
I configured a maven settings and global settings file in the Pipeline Maven Configuration of the folder containing the multibranch pipeline job. When I run the following stage from my Jenkins file:
stage('Package') { steps { withMaven() { bat "set MAVEN ${env.MAVEN_VERBOSE} clean package ${env.RELEASE_VERSION_PARAMETERS}" }
} }
I get this error:
[ERROR] Error executing Maven. [ERROR] The specified user settings file does not exist: e:\cc-build\checkout\aws\dctl\branchespackageFspring-boot\workspace@tmp\withMaven22e2d518\settings.xml
[JIRA] (JENKINS-57279) Github Organization PRs not building on agents
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57279 Github Organization PRs not building on agents Change By: Liam Newman Attachment: Screen Shot 2019-05-03 at 7.50.54 AM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57279) Github Organization PRs not building on agents
Title: Message Title Liam Newman commented on JENKINS-57279 Re: Github Organization PRs not building on agents Have you set master to not allow builds unless the specifically target master? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35642) Multibranch plugin is missing "Discard Old Builds"
Title: Message Title
Raphael Reitzig edited a comment on JENKINS-35642
Re: Multibranch plugin is missing "Discard Old Builds"
For fellow googlers: in a declarative pipeline, use something like{code}options {buildDiscarder(logRotator(artifactDaysToKeepStr: '17',artifactNumToKeepStr: '7',daysToKeepStr: '100',numToKeepStr: '100'))}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35642) Multibranch plugin is missing "Discard Old Builds"
Title: Message Title
Raphael Reitzig commented on JENKINS-35642
Re: Multibranch plugin is missing "Discard Old Builds"
For fellow googlers: in a declarative pipeline, use something like
options {
buildDiscarder(logRotator(
artifactDaysToKeepStr: '17',
artifactNumToKeepStr: '7',
daysToKeepStr: '100',
numToKeepStr: '100'
))
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57279) Github Organization PRs not building on agents
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57279 Github Organization PRs not building on agents Change By: Liam Newman Our Jenkins is running a Master > Slave Agent setup. Builds triggered by a push to one of the configured named branches works okay and the jobs run on the slaves agents . However, jobs triggered by a PR request are not being built on the slaves agents , but rather on the master, which is causing issues since our Master node is tiny, not meant to actually build.The master is configured to have 0 executors at the moment, but its still triggering the PR request build.Any help would be appreciated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57279) Github Organization PRs not building on agents
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57279 Github Organization PRs not building on agents Change By: Liam Newman Summary: Github Organization PRs not building on Slaves agents Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48802) Possibility to add/change the path that used to display source files
Title: Message Title Matthieu Brucher commented on JENKINS-48802 Re: Possibility to add/change the path that used to display source files eslint is run inside the container, the container itself is built at the beginning of the pipeline. As I can't assume that the Jenkins slave have all the required tools to run eslint, the proper way to go was to use a container that would retrieve the required modules. Just adding a way to reconnect the two paths would be enough, as the path inside the container (also used for the unit tests) is just a fraction of the actual workspace path. Basically just adding "folder/" as "folder" would be where I built the container. The Jenkins pipeline itself is run in the parent of "folder", I suspect that's why the checker cannot figure out where the files actually are. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Govind Sureka commented on JENKINS-57181 Re: Jenkins ALM disconnection Daniel, could you please check with UFT team for update on this issue. Its needs immediate attention. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Jesse Glick started work on JENKINS-57244 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-56996 null permission lookup when pull-request's origin repo/branch is deleted on github Change By: Liam Newman Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57323) "Last Console" button does not work for jobs inside a folder
Title: Message Title Micky Meyers updated an issue Jenkins / JENKINS-57323 "Last Console" button does not work for jobs inside a folder Change By: Micky Meyers It The "Last Console" button always links to */job/_$job_name_/lastBuild/console*.This doesn't work for jobs in folders.For jobs inside folders it should rather link to */job/_$folder_/job/_$job_name_/lastBuild/console*. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57323) "Last Console" button does not work for jobs inside a folder
Title: Message Title Micky Meyers updated an issue Jenkins / JENKINS-57323 "Last Console" button does not work for jobs inside a folder Change By: Micky Meyers The "Last Console" button always links to */job/_$job_name_/lastBuild/console*. This doesn't work gives a 404 for jobs in folders.For jobs inside folders it should rather link to */job/_$folder_/job/_$job_name_/lastBuild/console*. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48802) Possibility to add/change the path that used to display source files
Title: Message Title Ulli Hafner commented on JENKINS-48802 Re: Possibility to add/change the path that used to display source files Hmm, but how should adding a source code path help in your case? The files are fetched from the agent that contains the checkstyle.xml file. Is your workspace outside of the docker container? And how does eslint find the sources to check? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57323) "Last Console" button does not work for jobs inside a folder
Title: Message Title Micky Meyers created an issue Jenkins / JENKINS-57323 "Last Console" button does not work for jobs inside a folder Issue Type: Bug Assignee: Fred G Components: extra-columns-plugin Created: 2019-05-03 14:29 Environment: Jenkins v2.175 Folders plugin 6.8 (latest) Extra Columns Plugin v1.20 (latest) Priority: Major Reporter: Micky Meyers It always links to /job/$job_name/lastBuild/console. This doesn't work for jobs in folders. For jobs inside folders it should rather link to /job/$folder/job/$job_name/lastBuild/console. Add Comment
[JIRA] (JENKINS-57119) maven-plugin random socket leak, leading to threads leak on slave and master
Title: Message Title Gabriel Lavoie commented on JENKINS-57119 Re: maven-plugin random socket leak, leading to threads leak on slave and master Adding more information about TCP KeepAlive: https://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/ From HOWTO: Keepalive is non-invasive, and in most cases, if you're in doubt, you can turn it on without the risk of doing something wrong. But do remember that it generates extra network traffic, which can have an impact on routers and firewalls. In short, use your brain and be careful. In the next section we will distinguish between the two target tasks for keepalive: Checking for dead peers Preventing disconnection due to network inactivity To add some explanation on the configuration, when keep-alive is enabled on a socket, the Linux network stack will start sending empty PSH packets after 2 hours of inactivity (net.ipv4.tcp_keepalive_time) at a regular interval (net.ipv4.tcp_keepalive_intvl) expecting to receive an ACK. If the peer doesn't answer for a specific number of attempts (net.ipv4.tcp_keepalive_probes) or a RST is received, the network stack will know the connection is dead and it will report it to the application (IOException). We've been testing this change for a few weeks now and we don't see any adverse effect as those threads seems to be only linked to the slave, associated with jobs that completed successfully most of the time. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57119) maven-plugin random socket leak, leading to threads leak on slave and master
Title: Message Title Jesse Glick updated JENKINS-57119 Jenkins / JENKINS-57119 maven-plugin random socket leak, leading to threads leak on slave and master Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57119) maven-plugin random socket leak, leading to threads leak on slave and master
Title: Message Title Jesse Glick started work on JENKINS-57119 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57119) maven-plugin random socket leak, leading to threads leak on slave and master
Title: Message Title Jesse Glick assigned an issue to Gabriel Lavoie Jenkins / JENKINS-57119 maven-plugin random socket leak, leading to threads leak on slave and master Change By: Jesse Glick Assignee: Gabriel Lavoie Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-57244
java.io.NotSerializableException: The calling thread Thread has no associated channel
Change By:
Jesse Glick
after a successfull Excecution we get the following stacktrace: (rollback to jenkins 2.172 fixes the problem) {code:none} INFO: EXECUTION SUCCESS INFO: INFO: Total time: 1:16.948s INFO: Final Memory: 88M/6409M INFO: FATAL: java.lang.RuntimeException: Failed to serialize hudson.maven.MavenBuild#projectActionReporters for class hudson.maven.MavenBuild java.io.NotSerializableException: The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /data/jenkins/jobs/.../javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) at hudson.FilePath.writeObject(FilePath.java:2989) 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 com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:135) Caused: com.thoughtworks.xstream.converters.ConversionException: Could not call hudson.FilePath.writeObject() : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel Debugging information message : Could not call hudson.FilePath.writeObject() cause-exception : java.io.NotSerializableException cause-message : The calling thread Thread[Executor #0 for node : executing ... #5262,5,main|#5262,5,main] has no associated channel. The current object /path...$project/javadoc is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel --- at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteObject(SerializationMethodInvoker.java:141) at com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:259) at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:83) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at
[JIRA] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Title: Message Title Mike Baranczak commented on JENKINS-13140 Re: Disconnected slaves come back online within a few minutes +1. This is a bug, not a feature. If you click a button to disable a node, then a reasonable person would expect the node to stay disabled. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57322) "Build Current Patches Only" doesn't cancel the current running of old patchset when new patchset is comming.
Title: Message Title FEN WEI created an issue Jenkins / JENKINS-57322 "Build Current Patches Only" doesn't cancel the current running of old patchset when new patchset is comming. Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2019-05-03 13:44 Environment: jenkins:1.651.3 git:2.4.2 gerrit-trigger: 2.18.4 Priority: Major Reporter: FEN WEI According to history, both Patch set 1 and Patch set 3 ran at the same time. Actually, if we enabled the "Build current patchset only", the pat set 1 should be canceled if patch set 3 was added. But it seems not . This is may be a bug of gerrit trigger plugin, could you please help check? Add Comment
[JIRA] (JENKINS-56312) PCT not taking into account jdk version for detached plugins
Title: Message Title Oleg Nenashev commented on JENKINS-56312 Re: PCT not taking into account jdk version for detached plugins There was a bug in the implementation, fixed in https://github.com/jenkinsci/plugin-compat-tester/pull/140/commits/d6ce90e1c90a2db0f4b934ccc2784b66a26e8298 But JENKINS-57320 was introduced by another issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57322) "Build Current Patches Only" doesn't cancel the current running of old patchset when new patchset is comming.
Title: Message Title FEN WEI updated an issue Jenkins / JENKINS-57322 "Build Current Patches Only" doesn't cancel the current running of old patchset when new patchset is comming. Change By: FEN WEI Attachment: Capture.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57320 Fix a possible regression introduced on JENKINS-56312 Change By: Oleg Nenashev Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title Oleg Nenashev commented on JENKINS-57320 Re: Fix a possible regression introduced on JENKINS-56312 Pushed the fix directly to https://github.com/jenkinsci/plugin-compat-tester/pull/140 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title Oleg Nenashev updated JENKINS-57320 Jenkins / JENKINS-57320 Fix a possible regression introduced on JENKINS-56312 Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57258) Lost builds historical data after updating to Jenkins v2.175
Title: Message Title Devin Nusbaum commented on JENKINS-57258 Re: Lost builds historical data after updating to Jenkins v2.175 Based on those files, the pre-update run and flow execution have a result, the run is marked as completed and the flow execution is marked as done, which all looks good. The only things that seem off is that the flow execution does not have persistedClean = true, but that by itself shouldn't be a problem, and that the CloverHtmlBuildAction and checkout information were nulled out as part of the update. This does remind me of JENKINS-57254, which was also reported against 2.175 recently, although apparently that was caused by the SCoverage plugin which doesn't appear in your build.xml files. Do you see any errors in your Jenkins system logs around the time of the upgrade? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57258) Lost builds historical data after updating to Jenkins v2.175
Title: Message Title Nicolas Echegut commented on JENKINS-57258 Re: Lost builds historical data after updating to Jenkins v2.175 I grabbed the build.xml from a build before and after restart. I updated workflow-support from 3.2 to 3.3 right before upgrading Jenkins, but restarted Jenkins in-between. I was already on the latest version of workflow-job-plugin and workflow-cps-plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57258) Lost builds historical data after updating to Jenkins v2.175
Title: Message Title Nicolas Echegut updated an issue Jenkins / JENKINS-57258 Lost builds historical data after updating to Jenkins v2.175 Change By: Nicolas Echegut Attachment: build_after.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57258) Lost builds historical data after updating to Jenkins v2.175
Title: Message Title Nicolas Echegut updated an issue Jenkins / JENKINS-57258 Lost builds historical data after updating to Jenkins v2.175 Change By: Nicolas Echegut Attachment: build_before.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57317) Exception when checking 'Validate S3 Bucket configuration'
Title: Message Title Jesse Glick commented on JENKINS-57317 Re: Exception when checking 'Validate S3 Bucket configuration' If you are sure you granted all permissions to the role, then my first guess offhand would be that Jenkins is failing to pass the right region to the request, which may make it impossible for me to reproduce with the account I use for testing since I suppose you are using a European region. Will try to set up a reproduction environment at some point. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title Oleg Nenashev commented on JENKINS-57320 Re: Fix a possible regression introduced on JENKINS-56312 Also, there is a nice log entry there: "Not adding jaxb 2.163 2.3.0 11 as split because jdk specified 11 is newer than running jdk 11". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title Oleg Nenashev commented on JENKINS-57320 Re: Fix a possible regression introduced on JENKINS-56312 I was able to reproduce the issue, looking at the root cause Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title Oleg Nenashev started work on JENKINS-57320 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-57320
Fix a possible regression introduced on JENKINS-56312
Change By:
Baptiste Mathus
[~batmat] has worked on adding integration tests to PCT. This is done in this PR: [https://github.com/jenkinsci/plugin-compat-tester/pull/140]With this PR, the Jenkinsfile of PCT runs a test well known to be successful on Java 8 and Java 11.But when testing this PR and a previous one ([https://github.com/jenkinsci/plugin-compat-tester/pull/133]) we found out that PCT fails because it hasn't run any test.In the PR #133 Baptiste reverted the changes on [https://github.com/jenkinsci/plugin-compat-tester/pull/115] and the integration test for PCT ran successfully. So it seems that there is something wrong with this PR (#133).This task is to look into it and fix the problem. h3. Acceptance criteria:* Create a PR with a fix that makes the Integration Tests introduced on PR #140 run successfully h3. ReproducerCurrently, the following command exits immediately without running any test at all:{noformat}$ curl -sL http://mirrors.jenkins.io/war-stable/2.164.2/jenkins.war --output jenkins.war$ docker run --rm -ti \ -v maven-repo:/root/.m2 -v $(pwd)/jenkins.war:/pct/jenkins.war:ro \ -v $(pwd)/out:/pct/out -e JDK_VERSION=11 \ -e ARTIFACT_ID=buildtriggerbadge -e VERSION=buildtriggerbadge-2.10 \ jenkins/pct@sha256:caafc379935bae50f77aad8df680b74f79f0f73bec77ae95740e73fa2a22f476+ '[' 0 -eq 1 ']'+ '[' -n buildtriggerbadge ']'+ echo 'Running PCT for plugin buildtriggerbadge'Running PCT for plugin buildtriggerbadge+ CUSTOM_MAVEN_SETTINGS=/pct/m2-settings.xml+ FAIL_ON_ERROR_ARG=+ '[' -n '' ']'+ FAIL_ON_ERROR_ARG=-failOnError+ '[' -f /pct/m2-settings.xml ']'+ MVN_SETTINGS_FILE=/pct/default-m2-settings.xml+ '[' -n '' ']'+ '[' -z buildtriggerbadge ']'+ CHECKOUT_SRC=https://github.com/jenkinsci/buildtriggerbadge-plugin.git+ '[' -f /pct/jenkins.war ']'+ mkdir -p /pct/tmp+ cp /pct/jenkins.war /pct/tmp/jenkins.war+ JENKINS_WAR_PATH=/pct/tmp/jenkins.war+ WAR_PATH_OPT='-war /pct/tmp/jenkins.war '++ groovy /pct/scripts/readJenkinsVersion.groovy /pct/tmp/jenkins.war+ JENKINS_VERSION=2.164.2+ echo 'Using custom Jenkins WAR v. 2.164.2 from /pct/tmp/jenkins.war'Using custom Jenkins WAR v. 2.164.2 from /pct/tmp/jenkins.war+ [[ 2.164.2 =~ .*SNAPSHOT.* ]]+ SHOULD_CHECKOUT=1+ '[' -z buildtriggerbadge-2.10 ']'+ echo 'Will be testing with buildtriggerbadge:buildtriggerbadge-2.10, shouldCheckout=1'Will be testing with buildtriggerbadge:buildtriggerbadge-2.10, shouldCheckout=1+ extra_java_opts=()+ [[ -n '' ]]+ LOCAL_CHECKOUT_ARG=+ '[' 1 -eq 1 ']'+ '[' -z '' ']'+ mkdir -p /pct/tmp/localCheckoutDir+ cd /pct/tmp/localCheckoutDir+ TMP_CHECKOUT_DIR=/pct/tmp/localCheckoutDir/undefined+ '[' -e /pct/plugin-src/pom.xml ']'+ echo 'Checking out from https://github.com/jenkinsci/buildtriggerbadge-plugin.git:buildtriggerbadge-2.10'Checking out from
[JIRA] (JENKINS-57321) Cannot set diferent shebang in shell in Docker in pipeline
Title: Message Title Carlos Sanchez commented on JENKINS-57321 Re: Cannot set diferent shebang in shell in Docker in pipeline have you tried without the new line? sh """#!/bin/sh Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47896) Jenkins core classes should implement SerializableOnlyOverRemoting
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47896 Jenkins core classes should implement SerializableOnlyOverRemoting Change By: Oleg Nenashev Labels: causes-regression remoting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-57320 Fix a possible regression introduced on JENKINS-56312 Issue Type: Bug Assignee: Unassigned Components: plugin-compat-tester Created: 2019-05-03 12:31 Labels: java11 java11-devtools-compatibility triaged Priority: Major Reporter: Ramon Leon Baptiste Mathus has worked on adding integration tests to PCT. This is done in this PR: https://github.com/jenkinsci/plugin-compat-tester/pull/140 With this PR, the Jenkinsfile of PCT runs a test well known to be successful on Java 8 and Java 11. But when testing this PR and a previous one (https://github.com/jenkinsci/plugin-compat-tester/pull/133) we found out that PCT fails because it hasn't run any test. In the PR #133 Baptiste reverted the changes on https://github.com/jenkinsci/plugin-compat-tester/pull/115 and the integration test for PCT ran successfully. So it seems that there is something wrong with this PR (#133). This task is to look into it and fix the problem. Acceptance criteria: Create a PR with a fix that makes the Integration Tests introduced on PR #140 run successfully
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-57320 Fix a possible regression introduced on JENKINS-56312 Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
