[JIRA] (JENKINS-54556) The authorizationMatrix plugin doesent work with pipeline
Title: Message Title Daniel Beck commented on JENKINS-54556 Re: The authorizationMatrix plugin doesent work with pipeline Would not be surprised if this ends up being the same problem as JENKINS-47697 and JENKINS-47885, as in all cases, IIRC, the problem is the insertion of a matrix-auth configuration that wasn't in the DOM already when the page loaded. 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-54556) The authorizationMatrix plugin doesent work with pipeline
Title: Message Title
Daniel Beck edited a comment on JENKINS-54556
Re: The authorizationMatrix plugin doesent work with pipeline
It appears to be a _javascript_ problem:{noformat}TypeError: master is null {noformat} Probably due to [https://github.com/jenkinsci/matrix-auth-plugin/blob/2be2070e8023219c2b8d70e8e09be1dd757c2702/src/main/resources/hudson/security/GlobalMatrixAuthorizationStrategy/config.jelly#L144]
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-54556) The authorizationMatrix plugin doesent work with pipeline
Title: Message Title Daniel Beck commented on JENKINS-54556 Re: The authorizationMatrix plugin doesent work with pipeline It appears to be a _javascript_ problem: TypeError: master is null 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-54566) Failed to execute command Pipe.Flush
Title: Message Title Andrew Widdersheim created an issue Jenkins / JENKINS-54566 Failed to execute command Pipe.Flush Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2018-11-10 17:00 Environment: Running Jenkins in Docker on version 2.138.2. Running the Jenkins Slave Docker container using remoting version 3.27 Priority: Minor Reporter: Andrew Widdersheim Seeing this in my logs but for the most part everything seems to be working fine. I am sort of unclear on whether my Jenkins master is compatible with this agent version so that may be the problem. Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: This command is created here Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: Failed to execute command Pipe.Flush(-1) (channel Jenkins Agent (i-03788ba5fec517424)) java.util.concurrent.ExecutionException: Invalid object ID -1 iota=263 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:478) at hudson.remoting.ExportTable.get(ExportTable.java:397) at hudson.remoting.Channel.getExportedObject(Channel.java:780) at hudson.remoting.ProxyOutputStream$Flush.execute(ProxyOutputStream.java:307) at hudson.remoting.Channel$1.handle(Channel.java:565) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:87) Caused by: java.lang.Exception: Object appears to be deallocated at lease before Sat Nov 10 15:38:16 UTC 2018 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:474) ... 5 more Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: This command is
[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-53858 Re: Deadlock on EC2 resources I am testing as well the patch and for now seems working fine, 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-54401) NPE when parsing scm git revision date on PR branches
Title: Message Title Nikolas Falco updated JENKINS-54401 Jenkins / JENKINS-54401 NPE when parsing scm git revision date on PR branches Change By: Nikolas Falco 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-52696) Logstash Plugin: Incrementalify
Title: Message Title René Scheibe started work on JENKINS-52696 Change By: René Scheibe 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-54567) Last deployed/published/finished column
Title: Message Title Per Böhlin updated an issue Jenkins / JENKINS-54567 Last deployed/published/finished column Change By: Per Böhlin Most Jenkins jobs produce some kind of artifact, and the publication usually happens in the end of a build. From an artifact deployment/publishing perspective it is hence not very useful to learn when the last job started, or the last duration. Instead, more useful would be the time when that artifact was made available, approximated by the end of the build (start-time + duration). Usually artifacts are only published on successful builds. Therefore it would be most useful if only stable builds was considered (optionally configurable?). It would be great if the "extra-columns-plugin" could provide another extra column named "last published", "last deployed", "last finished" or similar, representing when the last (successful) job finished. Extra points if the name of the column is configurable. More extra points if the build-status is selectable (last stable, last unstable, last aborted, etc). 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
[JIRA] (JENKINS-54556) The authorizationMatrix plugin doesent work with pipeline
Title: Message Title Daniel Beck commented on JENKINS-54556 Re: The authorizationMatrix plugin doesent work with pipeline Andrew Bayer I'd like to note, however, that it works with the properties UI for the regular snippet generator. 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-52696) Logstash Plugin: Incrementalify
Title: Message Title René Scheibe assigned an issue to René Scheibe Jenkins / JENKINS-52696 Logstash Plugin: Incrementalify Change By: René Scheibe Assignee: René Scheibe 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-54548) Assistance with JQL Format
Title: Message Title Thomas Jones commented on JENKINS-54548 Re: Assistance with JQL Format Have you configured the JIRA credentials in Jenkins as per mentioned in my comment? If you mean in the https:///configure section, then, "yes, I believe so". Like I say, everything works unless I attempt to restrict things through the use of a JQL filter. What do you configure as the value of ISSUENAME? ISSUE in JQL accepts ISSUE_KEY. For example, the JQL for this current ticket is ISSUE=JENKINS-54548. I don't understand how would you use that field to filter your job trigger. Sorry, what I meant is that I was trying to configure my Jenkins job to only "listen" for the build-request string (in my test case, "BUILD ME NOW") only when it's present in the issue TEST-4, but to (essentially) ignore that same build-request string if it's commented into any other issue (e.g., if someone posted "BUILD ME NOW" into TEST-5 or Test-200, the job with the JQL-filter would ignore that comment). 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-52696) Logstash Plugin: Incrementalify
Title: Message Title René Scheibe updated JENKINS-52696 Jenkins / JENKINS-52696 Logstash Plugin: Incrementalify Change By: René Scheibe Status: In Review 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-52696) Logstash Plugin: Incrementalify
Title: Message Title René Scheibe updated JENKINS-52696 Jenkins / JENKINS-52696 Logstash Plugin: Incrementalify Change By: René Scheibe 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-54567) Last deployed/published/finished column
Title: Message Title Per Böhlin created an issue Jenkins / JENKINS-54567 Last deployed/published/finished column Issue Type: New Feature Assignee: Fred G Components: extra-columns-plugin Created: 2018-11-10 17:46 Priority: Minor Reporter: Per Böhlin Most Jenkins jobs produce some kind of artifact, and the publication usually happens in the end of a build. From an artifact deployment/publishing perspective it is hence not very useful to learn when the last job started, or the last duration. Instead, more useful would be the time when that artifact was available, approximated by the end-time (start-time + duration). It would be great if the "extra-columns-plugin" could provide another extra column named "last published", "last deployed", "last finished" or similar, representing when the last job finished. Extra points if the name of the column is configurable. Add Comment
[JIRA] (JENKINS-54548) Assistance with JQL Format
Title: Message Title Wisen Tanasa commented on JENKINS-54548 Re: Assistance with JQL Format Thanks for the detailed answer. Follow up questions: Have you configured the JIRA credentials in Jenkins as per mentioned in my comment? What do you configure as the value of ISSUENAME? ISSUE in JQL accepts ISSUE_KEY. For example, the JQL for this current ticket is ISSUE=JENKINS-54548. I don't understand how would you use that field to filter your job trigger. Alternatively, if you are trying to differentiate by ISSUE, the plugin injects JIRA_ISSUE_KEY as an environment variable. Would it be possible to execute your build conditionally based on that environment variable? 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-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Tobias Gruetzmacher commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies I'm not sure if this is the same issue, but the git-plugin (master) includes the apache-httpcomponents-client-4-api plugin in it's test scope, which puts dependencies of that plugin into the final hpi. Here is a workaround using "optional" (which makes the thing even more ugly): https://github.com/jenkinsci/git-plugin/pull/606 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-54566) Failed to execute command Pipe.Flush
Title: Message Title
Andrew Widdersheim updated an issue
Jenkins / JENKINS-54566
Failed to execute command Pipe.Flush
Change By:
Andrew Widdersheim
Seeing this in my logs but for the most part everything seems to be working fine. I am sort of unclear on whether my Jenkins master is compatible with this agent version so that may be the problem. {noformat} Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: This command is created here Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: Failed to execute command Pipe.Flush(-1) (channel Jenkins Agent (i-03788ba5fec517424)) java.util.concurrent.ExecutionException: Invalid object ID -1 iota=263 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:478) at hudson.remoting.ExportTable.get(ExportTable.java:397) at hudson.remoting.Channel.getExportedObject(Channel.java:780) at hudson.remoting.ProxyOutputStream$Flush.execute(ProxyOutputStream.java:307) at hudson.remoting.Channel$1.handle(Channel.java:565) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:87) Caused by: java.lang.Exception: Object appears to be deallocated at lease before Sat Nov 10 15:38:16 UTC 2018 at hudson.remoting.ExportTable.diagnoseInvalidObjectId(ExportTable.java:474) ... 5 more Nov 10, 2018 3:58:44 PM hudson.remoting.Channel$1 handle SEVERE: This command is created here{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54567) Last deployed/published/finished column
Title: Message Title Per Böhlin updated an issue Jenkins / JENKINS-54567 Last deployed/published/finished column Change By: Per Böhlin Most Jenkins jobs produce some kind of artifact, and the publication usually happens in the end of a build. From an artifact deployment/publishing perspective it is hence not very useful to learn when the last job started, or the last duration. Instead, more useful would be the time when that artifact was made available, approximated by the end -time of the build (start-time + duration).It would be great if the "extra-columns-plugin" could provide another extra column named "last published", "last deployed", "last finished" or similar, representing when the last job finished. Extra points if the name of the column is configurable. 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-54412) Testng Plugin should have capability to save the reports in
Title: Message Title Nalin Makar commented on JENKINS-54412 Re: Testng Plugin should have capability to save the reports in Rati Saxena, I am not maintaining this plugin much. If you create a PR, I can help with getting it merged in. BTW, looks like you are doing something non-standard. TestNG plugin is figuring out the build dir from the job itself. So, there should be no need to specify `testngdir`. Follow the breadcrumbs in Publisher.java. 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-54556) The authorizationMatrix plugin doesent work with pipeline
Title: Message Title
Sergey Bralgin commented on JENKINS-54556
Re: The authorizationMatrix plugin doesent work with pipeline
Daniel Beck Andrew Bayer Guys, thank you a lot for your help. I found solution, I just misconfigured my Pipeline Job. Maybe it will be good example for another men. Working pipeline Jobs looks like (I just moved properties() parameter to "script part"):
pipeline {
agent none
stages {
stage('base matrix test') {
agent { node { label "jenkins-worker-ng" } }
steps {
script {
properties([authorizationMatrix(['hudson.model.Item.Build:Pupkin'])])
sh "echo matrix works!!"
}
}
}
}
}
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-13687) CSS addition for full-screen dashboard view (including an edit configuration link)
Title: Message Title Tobias Gruetzmacher updated JENKINS-13687 Fixed in dashboard-view plugin 2.10. Jenkins / JENKINS-13687 CSS addition for full-screen dashboard view (including an edit configuration link) Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved 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-52170) For Dashboard View plugin, how can I edit the view when 'Full screen view - hide standard Jenkins panels' is seletced
Title: Message Title Tobias Gruetzmacher updated JENKINS-52170 Fixed in dashboard-view plugin 2.10. Jenkins / JENKINS-52170 For Dashboard View plugin, how can I edit the view when 'Full screen view - hide standard Jenkins panels' is seletced Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved 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-49745) Too many CrumbFilter log entries per second
Title: Message Title Tobias Gruetzmacher updated JENKINS-49745 Fixed in dashboard-view plugin 2.10. Jenkins / JENKINS-49745 Too many CrumbFilter log entries per second Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved 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-39941) Empty areas in the full screen mode of Dashboard view plugin
Title: Message Title Tobias Gruetzmacher updated JENKINS-39941 Fixed in dashboard-view plugin 2.10. Jenkins / JENKINS-39941 Empty areas in the full screen mode of Dashboard view plugin Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved 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-54559) Build result regression since pipeline-maven 3.5.15 for failing tests (UNSTABLE)
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-54559 Build result regression since pipeline-maven 3.5.15 for failing tests (UNSTABLE) Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-54412) Testng Plugin should have capability to save the reports in
Title: Message Title Nalin Makar assigned an issue to Unassigned Jenkins / JENKINS-54412 Testng Plugin should have capability to save the reports in Change By: Nalin Makar Assignee: Nalin Makar 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-36730) Need to allow full sem versions like Nuget
Title: Message Title Andrew Sumner resolved as Fixed Jenkins / JENKINS-36730 Need to allow full sem versions like Nuget Change By: Andrew Sumner Status: Open Resolved Resolution: Fixed 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-36730) Need to allow full sem versions like Nuget
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-36730 Need to allow full sem versions like Nuget Change By: Andrew Sumner Status: Resolved 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-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-37193 inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Change By: Andrew Sumner Status: Resolved 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-54556) The authorizationMatrix plugin doesent work with pipeline
Title: Message Title Daniel Beck closed an issue as Not A Defect Not a defect. Any documentation deficits would be on the side of pipeline/declarative pipeline, and the JS error is filed as JENKINS-54568. Jenkins / JENKINS-54556 The authorizationMatrix plugin doesent work with pipeline Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect 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-49691) FilePath.installIfNecessaryFrom always download even if target already exists
Title: Message Title C R commented on JENKINS-49691 Re: FilePath.installIfNecessaryFrom always download even if target already exists Hi Cyril MARIN I looked at the code and you're right. The "last-modified" http header is missing. Now, we could add a condition to check if the "file exists locally and http header missing" then skip download, but this is wrong because if the remote file is updated, Jenkins will not download the fresh copy and assume we already have the updated copy. So I think this issue should be closed since the problem lies outside Jenkins. 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-36730) Need to allow full sem versions like Nuget
Title: Message Title Andrew Sumner commented on JENKINS-36730 Re: Need to allow full sem versions like Nuget Just released version 1.1 of the pugin to support this. The plugin no longer does any validation of the version number, but relies on ProGet to return an error if the version format is incorrect. 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-54184) manager.removeSummaries() throws UnsupportedOperationException
Title: Message Title Anudeep Lalam edited a comment on JENKINS-54184 Re: manager.removeSummaries() throws UnsupportedOperationException [~kchuriumova] : When are we you going to release a new version of this plugin? Our project is completely blocked because of this 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-54184) manager.removeSummaries() throws UnsupportedOperationException
Title: Message Title Anudeep Lalam commented on JENKINS-54184 Re: manager.removeSummaries() throws UnsupportedOperationException Kseniia Churiumova : When are we going to release a new version of this plugin? Our project is completely blocked because of this 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-54568) authorizationMatrix does not work in declarative snippet generator
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-54568 authorizationMatrix does not work in declarative snippet generator Issue Type: Bug Assignee: Daniel Beck Components: matrix-auth-plugin Created: 2018-11-11 07:45 Priority: Minor Reporter: Daniel Beck As discovered in comments to JENKINS-54556, a _javascript_ problem prevents authorizationMatrix from working in the declarative options generator. Likely related to the other _javascript_ problems. Add Comment This message
[JIRA] (JENKINS-54568) authorizationMatrix does not work in declarative snippet generator
Title: Message Title
Daniel Beck updated an issue
Jenkins / JENKINS-54568
authorizationMatrix does not work in declarative snippet generator
Change By:
Daniel Beck
As discovered in comments to JENKINS-54556, a _javascript_ problem prevents {{authorizationMatrix}} from working in the declarative {{options}} generator.Likely related to the other _javascript_ problems. {noformat}TypeError: master is null {noformat} Probably due to [https://github.com/jenkinsci/matrix-auth-plugin/blob/2be2070e8023219c2b8d70e8e09be1dd757c2702/src/main/resources/hudson/security/GlobalMatrixAuthorizationStrategy/config.jelly#L144]Would not be surprised if this ends up being the same problem as JENKINS-47697 and JENKINS-47885, as in all cases, IIRC, the problem is the insertion of a matrix-auth configuration that wasn't in the DOM already when the page loaded.
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-54559) Build result regression since pipeline-maven 3.5.15 for failing tests (UNSTABLE)
Title: Message Title Cyrille Le Clerc commented on JENKINS-54559 Re: Build result regression since pipeline-maven 3.5.15 for failing tests (UNSTABLE) Strange, even if I removed the comment "TODO: Once JENKINS-43995..." the logic is still the same. I'm adding troubleshooting logs. see https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-54559 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-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-53336 inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster Change By: Andrew Sumner Status: Resolved 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-42036) As a User I want to be able to pass variables when using the Deploy to Stage function
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-42036 As a User I want to be able to pass variables when using the Deploy to Stage function Change By: Andrew Sumner Status: Resolved 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-45578) As a user I want to be able to deploy to a stage even if that stage has deployed before
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-45578 As a user I want to be able to deploy to a stage even if that stage has deployed before Change By: Andrew Sumner Status: Resolved 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-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-54286 Unable to use variable tokens as build property values in Create Package in Declarative Script Change By: Andrew Sumner Status: Resolved 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-53336) inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster
Title: Message Title Andrew Sumner resolved as Fixed Jenkins / JENKINS-53336 inedo-buildmaster - trigger deployment always returns that job was aborted if job had warnings on BuildMaster Change By: Andrew Sumner Status: Open Resolved Resolution: Fixed 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-45498) During Plugin Execution log shows ProGet not BuildMaster
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-45498 During Plugin Execution log shows ProGet not BuildMaster Change By: Andrew Sumner Status: Resolved 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-50976) At end of build plugin is querying BuildMaster for apps deployable info
Title: Message Title Andrew Sumner commented on JENKINS-50976 Re: At end of build plugin is querying BuildMaster for apps deployable info Is this still happening or can the issue be 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-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Andrew Sumner resolved as Fixed Jenkins / JENKINS-54286 Unable to use variable tokens as build property values in Create Package in Declarative Script Change By: Andrew Sumner Status: Open Resolved Resolution: Fixed 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-38633) As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline.
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-38633 As a user I want to be able to start a specific stage of a BuildMaster Deployment pipeline. Change By: Andrew Sumner Status: Resolved 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-53263) indeo-buildmaster Create Package not passing variables
Title: Message Title Andrew Sumner closed an issue as Fixed Jenkins / JENKINS-53263 indeo-buildmaster Create Package not passing variables Change By: Andrew Sumner Status: Resolved 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.
