[JIRA] (JENKINS-53143) EnvInject converts all exception types into EnvInjectException
Title: Message Title Oleg Nenashev commented on JENKINS-53143 Re: EnvInject converts all exception types into EnvInjectException AbortException can be propagated directly in the referenced code, I will accept the pull request if you propose it. RejectedAccessException is a bit more tricky, because the API cannot be easily extended in a compatible way. What's wrong with wrapping it by a EnvInjectException from your PoV? The cause can be still analyzed from UI / code if needed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53152) MultiBranch Pipeline repository scan broken
Title: Message Title kgiloo created an issue Jenkins / JENKINS-53152 MultiBranch Pipeline repository scan broken Issue Type: Bug Assignee: Stephen Connolly Components: credentials-plugin Created: 2018-08-21 05:31 Environment: jenkins 2.133 Debian GNU/Linux 9 (stretch) credentials plugin 2.1.18 Pipeline Multibranch plugin 2.20 Priority: Critical Reporter: kgiloo Setup: multibranch pipeline based on subversion 1.8 after upgrading to credentials-plugin 2.1.18, my project is not scanned anymore, eventually displayed "NOT_BUILT". related log: Aug 20, 2018 7:45:00 AM jenkins.branch.MultiBranchProject$BranchIndexing run INFO: MY_MULTIBRANCH #20180820.074500 branch indexing action completed: NOT_BUILT in 47 ms Aug 20, 2018 7:45:00 AM hudson.model.Executor finish1 SEVERE: Executor threw an exception java.lang.LinkageError: com/cloudbees/plugins/credentials/domains/URIRequirementBuilder at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:337) at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:240) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:357) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:267) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633)
[JIRA] (JENKINS-53151) withContext not working as expected in combination with consoleLogFilter
Title: Message Title
roel postelmans updated an issue
Jenkins / JENKINS-53151
withContext not working as expected in combination with consoleLogFilter
Change By:
roel postelmans
I'm trying to make a custom ConsoleLogFilter in my pipeline script, however for some reason it breaks the echo functionality. Here's my code:{code:java} final class TestStream extends OutputStream { private final OutputStream delegate; TestStream(OutputStream delegate) {this.delegate = delegate } public void write(int b) throws IOException {delegate.write(b); } public void write(byte[] b) throws IOException {delegate.write(b); } public void write(byte[] b, int off, int len) throws IOException {delegate.write(b, off, len); } public void flush() throws IOException {delegate.flush(); } public void close() throws IOException {delegate.close(); }}class TestFilter extends ConsoleLogFilter { @Overridepublic OutputStream decorateLogger(AbstractBuild build, OutputStream logger)throws IOException, InterruptedException {if (logger == null) {return null;} return new TestStream(logger)}} ConsoleLogFilter subsequent = new TestFilter();ConsoleLogFilter original = getContext(ConsoleLogFilter.class);println original //prints nulltimestamps {original = getContext(ConsoleLogFilter.class);println original //prints TimestampNotesConsoleLogFilter objectecho "Out of Context" //VisiblewithContext(BodyInvoker.mergeConsoleLogFilters(original, subsequent)) {echo "In context " //Not visible}withContext(new TestFilter()) {echo "In context " //Not visible}}{code}Here is the output:{code:java}Started by user jenkinsRunning in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] getContext[Pipeline] echonull[Pipeline] timestamps[Pipeline] {[Pipeline] getContext[Pipeline] echo07:22:58 hudson.plugins.timestamper.pipeline.TimestamperStep$TimestampNotesConsoleLogFilter@1d678d7a[Pipeline] echo07:22:58 Out of Context[Pipeline] withContext[Pipeline] {[Pipeline] echo[Pipeline] }[Pipeline] // withContext[Pipeline] withContext[Pipeline] {[Pipeline] echo[Pipeline] }[Pipeline] // withContext[Pipeline] }[Pipeline] // timestamps[Pipeline] End of PipelineFinished: SUCCESS{code} The 'in context' print is never written to the outputstream
[JIRA] (JENKINS-53151) withContext not working as expected in combination with consoleLogFilter
Title: Message Title
roel postelmans created an issue
Jenkins / JENKINS-53151
withContext not working as expected in combination with consoleLogFilter
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline, pipeline-model-definition-plugin
Created:
2018-08-21 05:25
Labels:
jenkins console consoleoutput pipeline
Priority:
Major
Reporter:
roel postelmans
I'm trying to make a custom ConsoleLogFilter in my pipeline script, however for some reason it breaks the echo functionality. Here's my code:
final class TestStream extends OutputStream { private final OutputStream delegate; TestStream(OutputStream delegate) {
this.delegate = delegate
} public void write(int b) throws IOException {
delegate.write(b);
} public void write(byte[] b) throws IOException {
delegate.write(b);
}
public void write(byte[] b, int off, int len) throws IOException {
delegate.write(b, off, len);
} public void flush() throws IOException {
delegate.flush();
} public void close() throws IOException {
delegate.close();
}
}
class TestFilter extends ConsoleLogFilter { @Override
public OutputStream decorateLogger(AbstractBuild build, OutputStream logger)
throws IOException, InterruptedException {
if (logger == null) {
return null;
}
return new TestStream(logger)
}
}ConsoleLogFilter subsequent = new TestFilter();
ConsoleLogFilter original = getContext(ConsoleLogFilter.class);
println original //prints null
timestamps {
original = getContext(ConsoleLogFilter.class);
println original //prints
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Li Chang reopened an issue Hi Oliver, Seems the issue still not fixed, I tried your attached hpi, and installed on two Jenkins servers, both of them are using proxy. But it still raise "java.net.SocketTimeoutException" on the Jira configuration in Jenkins. In the plugin configuration page, with the proxy setting, it can access our Jira instance. But anyway it can't pass the validation on Jira server configuration. I would suggest maybe it can add two more fields "proxy host" and "proxy port" in the Jira server configuration section. Thanks. Regards, Li Chang Jenkins / JENKINS-25829 Proxy configuration does not work Change By: Li Chang Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you 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-53092) Unable to launch agent. It is refreshing screen for longer time
Title: Message Title Daniel Gront assigned an issue to Unassigned Jenkins / JENKINS-53092 Unable to launch agent. It is refreshing screen for longer time Change By: Daniel Gront Assignee: Daniel Gront Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52773) Upgrade to newer version
Title: Message Title Daniel Gront closed an issue as Fixed The issue is resolved. Jenkins / JENKINS-52773 Upgrade to newer version Change By: Daniel Gront Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53092) Unable to launch agent. It is refreshing screen for longer time
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53092 Unable to launch agent. It is refreshing screen for longer time Change By: Daniel Gront Component/s: core Component/s: hp-application-automation-tools-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53092) Unable to launch agent. It is refreshing screen for longer time
Title: Message Title Daniel Gront commented on JENKINS-53092 Re: Unable to launch agent. It is refreshing screen for longer time The following issue is not at the plugin but at Jenkins itself, I am removing the ticket from the plugin. FYI try to follow this https://wiki.jenkins.io/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines+on+Windows Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51707) Failure - java.net.SocketException: Connection reset
Title: Message Title Daniel Gront commented on JENKINS-51707 Re: Failure - java.net.SocketException: Connection reset Cooltey Feng, Have you tried configuring proxy at the Manage Plugins -> Advanced section? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51164) JIRA plugin doesn't honor proxy excludes
Title: Message Title Olivier Lamy updated JENKINS-51164 Jenkins / JENKINS-51164 JIRA plugin doesn't honor proxy excludes Change By: Olivier Lamy Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53150) Remove Perforce Plugin dependency
Title: Message Title Olivier Lamy updated JENKINS-53150 Jenkins / JENKINS-53150 Remove Perforce Plugin dependency Change By: Olivier Lamy Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53150) Remove Perforce Plugin dependency
Title: Message Title Olivier Lamy started work on JENKINS-53150 Change By: Olivier Lamy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53150) Remove Perforce Plugin dependency
Title: Message Title Olivier Lamy commented on JENKINS-53150 Re: Remove Perforce Plugin dependency pr https://github.com/jenkinsci/jira-plugin/pull/161 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53150) Remove Perforce Plugin dependency
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-53150 Remove Perforce Plugin dependency Change By: Olivier Lamy Security advisory: https://jenkins.io/security/advisory/2018-03-26/#SECURITY-536 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53150) Remove Perforce Plugin dependency
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-53150 Remove Perforce Plugin dependency Issue Type: Task Assignee: Olivier Lamy Components: jira-plugin Created: 2018-08-21 03:47 Labels: jira-plugin-3.0.1 Priority: Minor Reporter: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-52944) Test duration is always displayed as <1s
Title: Message Title Craig Rodrigues updated JENKINS-52944 Fix has been merged: https://github.com/jenkinsci/blueocean-plugin/pull/1794 Jenkins / JENKINS-52944 Test duration is always displayed as <1s Change By: Craig Rodrigues Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53149) GitHubCommitStatusSetter is not reading proper commit id from a shared library
Title: Message Title
Manuel de la Peña created an issue
Jenkins / JENKINS-53149
GitHubCommitStatusSetter is not reading proper commit id from a shared library
Issue Type:
Improvement
Assignee:
Kirill Merkushev
Components:
github-plugin
Created:
2018-08-21 01:45
Labels:
shared-libraries github
Priority:
Minor
Reporter:
Manuel de la Peña
I have this code in a shared library:
String getGitAuthor() {
def commit = sh(returnStdout: true, script: 'git rev-parse HEAD');
return sh(returnStdout: true, script: "git --no-pager show -s --format='%an' ${commit}").trim();
}
String getLastCommitMessage() {
return sh(returnStdout: true, script: 'git log -1 --pretty=%B').trim();
}
When running a build consuming the library, then those methods return values for the shared library project, instead of the project that is actually being built. Maybe I'm doing it wrong and I'm not locating the code in the proper place, so please correct me if I'm wrong. Besides that, in the same scenario, GitHubCommitStatusSetter is not able to get a proper commitId to update the status on Github, because the commitId that is passed is the head commit for the shared library, instead of the project being built.
[JIRA] (JENKINS-34839) Add new provider UpstreamComitterSinceLastSuccess
Title: Message Title David van Laatum commented on JENKINS-34839 Re: Add new provider UpstreamComitterSinceLastSuccess Simple nobody has put in the time to code it Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49796) git fetch timeout
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-49796 git fetch timeout Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-20879 SSH Credentials (private key with passphrase) do not work Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Greg Patterson commented on JENKINS-48828 Re: Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Same issue Jenkins 2.124 Bitbucket Pipeline for Blue Ocean 1.7.2 (Latest 1.8.2 - no fix IDed) Bitbucket Branch Source Plugin 2.2.12 (Current) Bitbucket Plugin 1.1.8 (Current) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51707) Failure - java.net.SocketException: Connection reset
Title: Message Title Cooltey Feng commented on JENKINS-51707 Re: Failure - java.net.SocketException: Connection reset I have the same issue that cannot download the plugin. The issue is on a Mac server in our office. Maybe we have a proxy in our office, I am not sure. For troubleshooting, I've also installed the Jenkins on my Mac and I can download the plugin without any issues. One thing would like to discuss is that once I paste the link http://updates.jenkins-ci.org/download/plugins/mock-slave/1.12/mock-slave.hpi to the browsers (Chrome, Firefox, Safari), it will show an error message such as Failed to download. Does anyone have the same issue? Jenkins version: 2.138 Java version: 1.8 Mac OS: High Sierra 10.13.6 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10457) Full-screen portlet URL should not change every time a Dashboard View is edited
Title: Message Title Tobias Gruetzmacher assigned an issue to Tobias Gruetzmacher Jenkins / JENKINS-10457 Full-screen portlet URL should not change every time a Dashboard View is edited Change By: Tobias Gruetzmacher Assignee: Marco Ambu Tobias Gruetzmacher Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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 assigned an issue to Tobias Gruetzmacher Jenkins / JENKINS-13687 CSS addition for full-screen dashboard view (including an edit configuration link) Change By: Tobias Gruetzmacher Assignee: Marco Ambu Tobias Gruetzmacher Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29730) MSBuild compile warnings jobs showing up in Pylint and JSLint lists
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-29730 MSBuild compile warnings jobs showing up in Pylint and JSLint lists Is this still a problem? If it is, please provide some more information to debug this issue (screenshots, configuration files, etc.) That said, this sounds like a problem with one specific portlet, which is provided by the warnings-plugin and probably needs to be fixed there. Change By: Tobias Gruetzmacher Component/s: dashboard-view-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29730) MSBuild compile warnings jobs showing up in Pylint and JSLint lists
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-29730 MSBuild compile warnings jobs showing up in Pylint and JSLint lists Change By: Tobias Gruetzmacher Component/s: dashboard-view-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12863) dashboard - jobs list portlet - add summary statistics
Title: Message Title Tobias Gruetzmacher assigned an issue to Unassigned Pull requests welcome. Jenkins / JENKINS-12863 dashboard - jobs list portlet - add summary statistics Change By: Tobias Gruetzmacher Assignee: Marco Ambu Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12167) add a klocwork portlet to dashboard view
Title: Message Title Tobias Gruetzmacher assigned an issue to Unassigned Pull requests welcome. Jenkins / JENKINS-12167 add a klocwork portlet to dashboard view Change By: Tobias Gruetzmacher Priority: Major Minor Assignee: Peter Hayes Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44856) Hi Team, I recently added dashboard and sonar plugins to my Jenkins server and after a restart entire UI crashed , i can't see any GUI and jobs running on my server.
Title: Message Title Tobias Gruetzmacher closed an issue as Incomplete Unfortuntly, this issue doesn't contain enough information to pinpoint what exactly is wrong or which plugin caused the issue. If you can reproduce the issue, please reopen this. You can read https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue as a starting point on how to isolate the issue. Jenkins / JENKINS-44856 Hi Team, I recently added dashboard and sonar plugins to my Jenkins server and after a restart entire UI crashed , i can't see any GUI and jobs running on my server. Change By: Tobias Gruetzmacher Status: Open Closed Assignee: Praqma Support Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this
[JIRA] (JENKINS-34839) Add new provider UpstreamComitterSinceLastSuccess
Title: Message Title Jim Searle commented on JENKINS-34839 Re: Add new provider UpstreamComitterSinceLastSuccess Is there are reason this has never been released? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53137) Automated cases found, but I cannot find them in job workspace at Jenkins
Title: Message Title herman gomez updated an issue Jenkins / JENKINS-53137 Automated cases found, but I cannot find them in job workspace at Jenkins Change By: herman gomez Labels: plugin testlink Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49947) unclear usage of input step in declarative pipeline
Title: Message Title
Fernando Nasser commented on JENKINS-49947
Re: unclear usage of input step in declarative pipeline
Is it possible to distinguish between input {
manual approval of release } when {
the release is approved } and when { # the release is approved } input {
manual approval of release }
And make the order of appearance determine what prevails?
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42597) Percent character (%) in filenames is not url-encoded in the CHANGES page
Title: Message Title Mark Waite edited a comment on JENKINS-42597 Re: Percent character (%) in filenames is not url-encoded in the CHANGES page I've duplicated the problem with the [ JENKINS-42597 job|https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-42597-percent-in-changed-filename-not-escaped] and with the [JENKINS-42597 branch|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-42597] which creates a pipeline job in my Docker image. The steps I'd missed (note, this is not the complete set of steps to duplicate the problem, just the steps that I had failed to take from the user interface after defining the job):# Submit a change to the github repository# Poll the github repository for changes (in my case, in response to a notifyCommit)# Confirm the build ran to completion# Click the link for that specific build (number 12 in my case)# Click the Changes link, confirm the summary shows a change to build-100%-number# Click the link to build-100%-number, and see github report 404. Clicking the diff link in at least one of my jobs correctly navigates to the diff on githubYou can see the job definitions that show the problem in the [JENKINS-42597 branch|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-42597] in my jenkins-bugs repository and in the [JENKINS-42597 job|https://github.com/MarkEWaite/docker-lfs/tree/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-42597-percent-in-changed-filename-not-escaped] in my Docker image.Pictures captured the steps so that I'll remember them...# !step-01.PNG|thumbnail! # !step-02.PNG|thumbnail! # !step-03.PNG|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran updated an issue Jenkins / JENKINS-53148 downstream job nolonger triggered Change By: dan tran This is regression properly due to JENKINS-51680 where my downstream job depends on a maven module/artifact of the upstream snapshot Revert back 3.5.9 to get auto trigger working again Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran created an issue Jenkins / JENKINS-53148 downstream job nolonger triggered Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-08-20 21:12 Priority: Minor Reporter: dan tran This is regression properly due to JENKINS-51680 where my downstream job depends on a maven module/artifact of the upstream snapshot Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-52825) Blue Ocean - Need to see executors
Title: Message Title Craig Rodrigues commented on JENKINS-52825 Re: Blue Ocean - Need to see executors Keith Zantow do you have a screenshot of what https://github.com/jenkinci/blueocean-executor-info-plugin looked like? If you don't have enough cycles, I'd like to dust this code off, and submit a PR to merge it into the blueocean-dashboard in the blueocean-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor There is no setsid shell command on macOS, so you have to compile https://github.com/jerrykuch/ersatz-setsid locally (make setsid), but once you do that I would expect that you could just run `/path/to/setsid java -jar jenkins.war` and then run a build on on the master. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor There is no setsid shell command on macOS, so you have to compile https://github.com/jerrykuch/ersatz-setsid locally (make setsid), but once you do that I would expect that you could just run `/path/to/setsid java -jar jenkins.war` and then run a build on on the master. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Mark Waite commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase If the master is running as a service (for example, as installed by the rpm file on CentOS, the deb file on Debian, the pkg file on FreeBSD), then setsid is not needed. Services are already running without a controlling terminal. If the master is running in the foreground and your computer has a command `setsid` in the PATH, then you could pass the java property: org.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Mark Waite Yeah I think the setsid is probably affecting me because I am running Jenkins from the terminal. But my question would be how do I go about adding setsid on a master? I could normally add it onto the prefix to the agent but if I am doing a checkout on master then how would I add it? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor On my macOS master, it doesn't work for the reasons that Mark explained (the terminal is interactive, so it prompts for the key at the command line, which doesn't work). Once I used setsid and a local JNLP agent it worked fine. Are you getting a timeout, or a public key error? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Mark Waite commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase I have not checked the behavior of a master running on Windows, just agents on Windows. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Mark Waite commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor the crucial attribute is whether the process that invokes command line git (agent or master) has a controlling terminal attached. If you ran "jenkins.war" from the command line, then you were running in the foreground unless you took special steps like: prefix command with `setsid` redirect stdin from /dev/null (maybe, never tried this one, but think it should work) run in the background and redirect stdin from /dev/null (maybe, never tried this one, but think it should work) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Devin Nusbaumsorry missed this. I used ssh with private key when I did my test. That is interesting about the setsid but I was not actually doing this checkout on an agent and was instead doing it on the master. Did you guys run it on the master as well? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51680) Infinity Build Loop
Title: Message Title dan tran commented on JENKINS-51680 Re: Infinity Build Loop looks like this create regression where my downstream jobs are skipped with the bellow message in jenkins console log [withMaven] Not triggering [x » y » z » master] because it has dependencies in the downstream project list what does it mean? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Mark Waite commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Devin Nusbaum there is a setting in the git plugin which will prefix every command line git call with `setsid` (on platforms where a setsid program is available). However, it is a system property and not readily available to typical users. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53147 Rebrand from Essentials to Evergreen Change By: Baptiste Mathus Sprint: Evergreen - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Mark Waite Thanks for the pointer, I used https://github.com/jerrykuch/ersatz-setsid to run a JNLP agent on macOS using setsid and am no longer seeing errors on macOS using a credential of type 'SSH Username w/ Private Key' in Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen
Title: Message Title Baptiste Mathus assigned an issue to R. Tyler Croy Jenkins / JENKINS-53147 Rebrand from Essentials to Evergreen Change By: Baptiste Mathus Assignee: Baptiste Mathus R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53147) Rebrand from Essentials to Evergreen
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-53147 Rebrand from Essentials to Evergreen Issue Type: Epic Assignee: Baptiste Mathus Components: essentials-plugin, evergreen Created: 2018-08-20 19:58 Priority: Minor Reporter: Baptiste Mathus Essentials Jenkins plugin => rename the plugin display name change the artifactId (we generally do not do this, but I think in this case we should because it's 1) still early stage and 2) nobody is ever supposed to install this plugin manually anyway * Rename occurrences of Essentials to Evergreen in the plugin In the evergreen repo itself, we should probably also rename Essentials to Evergreen as much as possible. .../evergreen $ git grep -i essentials | wc -l 111
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Mark Waite commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Is your Jenkins server process or agent process running in the foreground? Meaning, was it started from a shell prompt and is still running from a shell prompt? JNLP agents might be started that way. Docker-based servers are commonly started that way. OpenSSH will prompt for interactive input of the passphrase if it detects a terminal attached to its standard input. The workaround for the agent is to prefix the JNLP start command with `setsid`. That detaches the terminal. OpenSSH won't see a terminal and thus won't prompt. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52803) IBM Application Security on Cloud plugin does not currently allow for third party code to be scanned
Title: Message Title Kevin Fealey commented on JENKINS-52803 Re: IBM Application Security on Cloud plugin does not currently allow for third party code to be scanned Hi Robert, Are you trying to create the IRX file to scan with Cloud? While it would be nice to update the plugin for that use case, I'm currently the only maintainer (I don't work for IBM), and I do not have the availability to do it at the moment, mostly because I do not have an environment available to test the latest version. If you're interested in contributing to the project, the github repo is here: https://github.com/jenkinsci/ibm-security-appscansource-scanner-plugin It would probably be a fairly easy update to add the checkbox and --thirdparty option. From a quick check, here's what I think you'd need to do: add the checkbox here: https://github.com/jenkinsci/ibm-security-appscansource-scanner-plugin/blob/master/src/main/resources/com/aspectsecurity/automationservices/plugins/jenkins/appscansource/AppScanSourceBuilder/config.jelly Set the checkbox value here: https://github.com/jenkinsci/ibm-security-appscansource-scanner-plugin/blob/master/src/main/java/com/aspectsecurity/automationservices/plugins/jenkins/appscansource/AppScanSourceBuilder.java in AppScanSourceBuilder (the DataBoundConstructor) then add the --thirdparty option to the cliScriptContent variable within in a conditional block in the perform method. That's assuming that the rest of the command would remain the same... if you're going to push it to Cloud scan, you may want to execute a different command entirely - I haven't used that part of the CLI, so I don't know. Anyway, if you want to modify the code, test it, and submit a pull request, I'll merge it in - maybe another branch, since I may not be able to test it myself.. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-53061) Jenkins failing to install plugins in setup wizard
Title: Message Title Oleg Nenashev edited a comment on JENKINS-53061 Re: Jenkins failing to install plugins in setup wizard Please provide system logs, there is bot not enough info to diagnose Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53061) Jenkins failing to install plugins in setup wizard
Title: Message Title Oleg Nenashev commented on JENKINS-53061 Re: Jenkins failing to install plugins in setup wizard Please provide system logs, there is bot enough info to diagnose Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Mark Waite commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase A bundle would be fine. After seeing this report, I ran passphrase based tests on Windows and Linux with different versions of command line git. All of them passed. I don't have a macOS machine available. The closest I have to macOS is my FreeBSD machine and it uses a passphrase protected private key as well as my Linux and Windows machines. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Devin Nusbaum commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Alex Taylor What is the error message you are seeing, and what credentials type are you using in Jenkins (username/password, ssh username w/ private key, etc.)? I was able to get things working on a Linux machine, and can try again on Windows shortly. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46757) new Properties() requires approval also of Properties.(Properties) overload
Title: Message Title Andrew Bayer resolved as Fixed Turns out this was the same thing as JENKINS-50380, and was fixed and released in script-security 1.43. Woo. Jenkins / JENKINS-46757 new Properties() requires approval also of Properties.(Properties) overload Change By: Andrew Bayer Status: In Progress Resolved Resolution: Fixed Released As: script-security 1.43 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53134) Git checkout fails when using an SSH key with a passphrase
Title: Message Title Alex Taylor commented on JENKINS-53134 Re: Git checkout fails when using an SSH key with a passphrase Mark WaiteDevin Nusbaum This is MacOS and I see the same behavior as the customer who was running on windows >Are you using a passphrase which includes a character that is special to the shell Password was `testing` in my case I have not tried in Linux yet but I can certainly do it if you like. Could I attach a bundle of my instance where I reproduced so you can spin up a copy? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46757) new Properties() requires approval also of Properties.(Properties) overload
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-46757 new Properties() requires approval also of Properties.(Properties) overload Change By: Andrew Bayer Assignee: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46757) new Properties() requires approval also of Properties.(Properties) overload
Title: Message Title Andrew Bayer started work on JENKINS-46757 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Enrique Canales updated an issue Jenkins / JENKINS-53146 TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step Change By: Enrique Canales Component/s: groovy-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Oleg Nenashev commented on JENKINS-53146 Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step I believe this is a Groovy plugin issue. Custom Tools plugin contributes env vars in a common way, I am not sure how it handles it Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49374) 'Could not find dependency command-launcher of [package]' for every installed plugin when trying to run the jenkins check for updates
Title: Message Title MichaelBreu commented on JENKINS-49374 Re: 'Could not find dependency command-launcher of [package]' for every installed plugin when trying to run the jenkins check for updates Hello, I experience the same problem. Plugin update is not working any more. "Update now" is not working any more. It claims " Update-Metadaten wurden zuletzt vor 4 Monate 8 Tage aktualisiert." (Update meta data was last updated 4 month 8 days before). When playing around with the update URL I get above message. But not always. Update-Metadaten wurden zuletzt vor 4 Monate 8 Tage aktualisiert. Update-Metadaten wurden zuletzt vor 4 Monate 8 Tage aktualisiert. Update-Metadaten wurden zuletzt vor 4 Monate 8 Tage aktualisiert." Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49374) 'Could not find dependency command-launcher of [package]' for every installed plugin when trying to run the jenkins check for updates
Title: Message Title MichaelBreu edited a comment on JENKINS-49374 Re: 'Could not find dependency command-launcher of [package]' for every installed plugin when trying to run the jenkins check for updates Hello, I experience the same problem. Plugin update is not working any more. "Update now" is not working any more. It claims " Update-Metadaten wurden zuletzt vor 4 Monate 8 Tage aktualisiert." (Update meta data was last updated 4 month 8 days before). When playing around with the update URL I get above message. But not always. Update-Metadaten wurden zuletzt vor 4 Monate 8 Tage aktualisiert. Update-Metadaten wurden zuletzt vor 4 Monate 8 Tage aktualisiert. Update-Metadaten wurden zuletzt vor 4 Monate 8 Tage aktualisiert." Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title
Enrique Canales created an issue
Jenkins / JENKINS-53146
TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Issue Type:
Bug
Assignee:
Oleg Nenashev
Attachments:
FreeEnvVar_Config__Jenkins_.png
Components:
customtools-plugin
Created:
2018-08-20 18:40
Priority:
Minor
Reporter:
Enrique Canales
Attempting to use the TOOLNAME_HOME variable within an Execute system Groovy script build step causes error due to no variable expansion. java.io.FileNotFoundException: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)
Add Comment
[JIRA] (JENKINS-53145) invalid_auth error with correct Slack Token, while uploading file into Slack
Title: Message Title Girish T P created an issue Jenkins / JENKINS-53145 invalid_auth error with correct Slack Token, while uploading file into Slack Issue Type: Bug Assignee: Shitij Goyal Attachments: image-2018-08-20-23-35-53-422.png Components: slack-uploader-plugin Created: 2018-08-20 18:06 Environment: Jenkins 2.107.1, Slack Uploader Plugin 1.7 Priority: Major Reporter: Girish T P We are unable to upload files into Slack, through this plugin due to invalid_auth error, though the Slack Token provided is valid. Add Comment
[JIRA] (JENKINS-53143) EnvInject converts all exception types into EnvInjectException
Title: Message Title Dana Goyette commented on JENKINS-53143 Re: EnvInject converts all exception types into EnvInjectException Another noteworthy exception type it eats: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52803) IBM Application Security on Cloud plugin does not currently allow for third party code to be scanned
Title: Message Title Robert Catalano commented on JENKINS-52803 Re: IBM Application Security on Cloud plugin does not currently allow for third party code to be scanned Hey, just wondering if any progress has been made on this? I'm happy to assist in solving this issue with the plugin if need be. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53144) Whenever Jenkins is restarted, any updates\additions to the VSTEST global settings are lost.
Title: Message Title Scott Cusson created an issue Jenkins / JENKINS-53144 Whenever Jenkins is restarted, any updates\additions to the VSTEST global settings are lost. Issue Type: Bug Assignee: Unassigned Components: vstestrunner-plugin Created: 2018-08-20 17:51 Environment: Jenkins 2.138 and VSTest plugin 1.0.7 Priority: Minor Reporter: Scott Cusson Whenever Jenkins is restarted, any updates\additions to the VSTEST settings on the Global Tool Configuration page under the VSTest Installations are lost and it returns to the DEFAULT. I manually have to re-add configs for VSTest 14 and 15. Add Comment
[JIRA] (JENKINS-53143) EnvInject converts all exception types into EnvInjectException
Title: Message Title Dana Goyette created an issue Jenkins / JENKINS-53143 EnvInject converts all exception types into EnvInjectException Issue Type: Bug Assignee: Unassigned Components: envinject-plugin Created: 2018-08-20 17:49 Environment: Jenkins ver. 2.138 Plugins: ace-editor 1.1 true ansicolor 0.5.3-SNAPSHOT (private-350138e2-dgoyette) true ant 1.8 true antisamy-markup-formatter 1.5 true any-buildstep 0.1 true apache-httpcomponents-client-4-api 4.5.5-3.0 true authentication-tokens 1.3 true badge 1.5 true blueocean 1.8.0 true blueocean-autofavorite 1.2.2 true blueocean-bitbucket-pipeline 1.8.0 true blueocean-commons 1.8.0 true blueocean-config 1.8.0 true blueocean-core-js 1.8.0 true blueocean-dashboard 1.8.0 true blueocean-display-url 2.2.0 true blueocean-events 1.8.0 true blueocean-git-pipeline 1.8.0 true blueocean-github-pipeline 1.8.0 true blueocean-i18n 1.8.0 true blueocean-jira 1.8.0 true blueocean-jwt 1.8.0 true blueocean-personalization 1.8.0 true blueocean-pipeline-api-impl 1.8.0 true blueocean-pipeline-editor 1.8.0 true blueocean-pipeline-scm-api 1.8.0 true blueocean-rest 1.8.0 true blueocean-rest-impl 1.8.0 true blueocean-web 1.8.0 true bouncycastle-api 2.16.3 true branch-api 2.0.20 true build-monitor-plugin 1.12+build.201805070054 true build-timeout 1.19 true buildresult-trigger 0.17 true buildtriggerbadge 2.9 true built-on-column 1.1 true categorized-view 1.10 true cloudbees-bitbucket-branch-source 2.2.12 true cloudbees-folder 6.5.1 true collapsing-console-sections 1.7.0 true command-launcher 1.2 true compact-columns 1.10 true conditional-buildstep 1.3.6 true config-file-provider 2.18 true copyartifact 1.41 true credentials 2.1.18 true credentials-binding 1.16 true cron_column 1.4 true cvs 2.14 true dashboard-view 2.9.11 true display-url-api 2.2.0 true docker-commons 1.13 true docker-workflow 1.17 true durable-task 1.25 true dynamic-axis 1.0.3 true dynamic_extended_choice_parameter 1.0.1 false elastic-axis 1.2 true email-ext 2.63 true email-ext-recipients-column 1.0 true envinject 2.1.6 true envinject-api 1.5 true excludeMatrixParent 1.1 true extended-choice-parameter 0.76 true external-monitor-job 1.7 true extra-columns 1.20 true ez-templates 1.3.2 true ezwall 0.3 true favorite 2.3.2 true filesystem_scm 2.1 true flexible-publish 0.15.2 true fstrigger 0.39 true git 3.9.1 true git-client 2.7.3 true git-parameter 0.9.3 true git-server 1.7 true github 1.29.2 true github-api 1.92 true github-branch-source 2.3.6 true groovy 2.0 true groovy-postbuild 2.4.1 true handlebars 1.1.1 true handy-uri-templates-2-api
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
[~vivek] As seen in my previous comment, when clicking on the upper stage it is giving me the details of the Parent stage ( * {color:#de350b}_Pushing 2 Tests | / TE1_{color} * ) instead of the child (*_PUSH TE1_*) and when selecting the bottom stage it is giving me the details of the right stage ({color:#00875a}*_PUSH TE2_*{color}) but with {color:#de350b} +*wrong status*+ {color} .
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title
Elie Kassis edited a comment on JENKINS-53129
Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
[~vivek] As seen in my previous comment, the issue is that in Blue Ocean, when clicking on the upper stage it is giving me the details of the Parent stage ({color:#de350b}_Pushing 2 Tests_ Tests | TE1_ {color}) instead of the child (*_PUSH TE1_*) and when selecting the bottom stage it is giving me the details of the right stage ({color:#00875a}*_PUSH TE2_*{color}) but with +*wrong status*+.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis edited a comment on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Sorry [~vivek], but this is not the case on my side my 2 stages are processing exactly the same jobs that takes 2 hours each, we are not talking about instantly status appearance . As shown in below screenshots, the processing stage that is showing wrong Passed status (PUSH TE2), is showing the triggered builds properly. As for the stage showing processing status (PUSH TE1), the Triggered Builds section does not exist.!image-2018-08-20-19-51-36-113.png|width=410,height=269!!image-2018-08-20-19-53-40-887.png|width=501,height=247! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52510) Logs contain garbage
Title: Message Title Stanislav Pugachov closed an issue as Not A Defect doc reference is https://javadoc.jenkins.io/hudson/console/AnnotatedLargeText.html Jenkins / JENKINS-52510 Logs contain garbage Change By: Stanislav Pugachov Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Vivek Pandey, as a summary the expected behavior is to show processing stages as Processing and to be able to access the Triggered Builds upon clicking on the stage. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52510) Logs contain garbage
Title: Message Title
Stanislav Pugachov edited a comment on JENKINS-52510
Re: Logs contain garbage
you are right,{code:java}def baos = new ByteArrayOutputStream()currentBuild.rawBuild.getLogText(). writeRawLogTo writeLogTo (0, baos)println(baos.toString()){code}works like a charm,Thanks, sorry for bothering.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis edited a comment on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Sorry [~vivek], but this is not the case on my side. As shown in below screenshots, the processing stage that is showing wrong Passed status (PUSH TE2) , is showing the triggered builds properly. As for the stage showing processing status (PUSH TE1) , the Triggered Builds section does not exist.!image-2018-08-20-19-51-36-113.png|width=410,height=269!!image-2018-08-20-19-53-40-887.png|width=501,height=247! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52510) Logs contain garbage
Title: Message Title Stanislav Pugachov commented on JENKINS-52510 Re: Logs contain garbage you are right, def baos = new ByteArrayOutputStream() currentBuild.rawBuild.getLogText().writeRawLogTo(0, baos) println(baos.toString()) works like a charm, Thanks, sorry for bothering. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis edited a comment on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Sorry [~vivek], but this is not the case on my side. As shown in below screenshot screenshots , the processing stage that is showing wrong status, is showing the triggered builds properly ; as . As for the stage showing processing status, the Triggered Builds are empty section does not exist .!image-2018-08-20-19-51-36-113.png|width=410,height=269!!image-2018-08-20-19-53-40-887.png|width=501,height=247! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Vivek Pandey As seen in my previous comment, the issue is that in Blue Ocean, when clicking on the upper stage it is giving me the details of the Parent stage (Pushing 2 Tests) instead of the child (PUSH TE1) and when selecting the bottom stage it is giving me the details of the right stage (PUSH TE2) but with wrong status. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Sorry Vivek Pandey, but this not the case on my side. As shown in below screenshot, the processing stage that is showing wrong status, is showing the triggered builds properly; as for the stage showing processing the Triggered Builds are empty. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Change By: Elie Kassis Attachment: image-2018-08-20-19-53-40-887.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-53129 View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Change By: Elie Kassis Attachment: image-2018-08-20-19-51-36-113.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52510) Logs contain garbage
Title: Message Title Oleg Nenashev commented on JENKINS-52510 Re: Logs contain garbage There is a way to do that. Run#getLogText().writePlainText or so. No access to the laptop now Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53142) Jenkins Blue Ocean will not reflect the stages in my jenkinsfile
Title: Message Title Pranavi Ireni created an issue Jenkins / JENKINS-53142 Jenkins Blue Ocean will not reflect the stages in my jenkinsfile Issue Type: Bug Assignee: Victor Martinez Components: jenkinslint-plugin Created: 2018-08-20 16:43 Priority: Critical Reporter: Pranavi Ireni Jenkins Blue Ocean won't reflect my pipeline and is failing at a particular stage each time without any changes being made to the script. The script works fine and has absolutely no errors in it. I want to know why my pipeline is not going past that specific stage. Add Comment
[JIRA] (JENKINS-52510) Logs contain garbage
Title: Message Title Stanislav Pugachov edited a comment on JENKINS-52510 Re: Logs contain garbage Hi [~oleg_nenashev], Thank you for your reply. Your solutions are not an options option for me because they require authentication.But i just want to collect the log programatically, preferably by groovy code-snippet.Is this possible?The only way I can see is [https://javadoc.jenkins-ci.org/hudson/model/Run.html#getLog-int-]But it doesn't solve the problem..Thats weird when job have no way to get its own "clean log" Thanks Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52510) Logs contain garbage
Title: Message Title Stanislav Pugachov edited a comment on JENKINS-52510 Re: Logs contain garbage Hi [~oleg_nenashev], Thank you for your reply. Your solutions are not an option for me because they require authentication.But i just want to collect the log programatically, preferably by groovy code-snippet.Is this possible?The only way I can see is [https://javadoc.jenkins-ci.org/hudson/model/Run.html#getLog-int-]But it doesn't solve the problem.. Thats Its weird when that ' job have ' has no way to get its own "clean log" Thanks Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52510) Logs contain garbage
Title: Message Title Stanislav Pugachov commented on JENKINS-52510 Re: Logs contain garbage Hi Oleg Nenashev, Thank you for your reply. Your solutions are not an options for me because they require authentication. But i just want to collect the log programatically, preferably by groovy code-snippet. Is this possible? The only way I can see is https://javadoc.jenkins-ci.org/hudson/model/Run.html#getLog-int- But it doesn't solve the problem.. Thats weird when job have no way to get its own "clean log" Thanks Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50730) NoClassDefFound errors in Cloud Slaves
Title: Message Title Jeff Thompson commented on JENKINS-50730 Re: NoClassDefFound errors in Cloud Slaves Alon Lavi, there are different opinions on how issue reports like this should be handled. I tend to follow the approach that if it cannot be sufficiently described and reproduced then it should be closed as cannot reproduce and then re-opened if someone obtains better information. Particularly when a significant number of the reporters have seen the problem go away from environmental or version changes. But, let's keep this one open for a while longer and see if we get any better information. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53141) Test results: cannot hyperlink directly to a log line
Title: Message Title Craig Rodrigues created an issue Jenkins / JENKINS-53141 Test results: cannot hyperlink directly to a log line Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-08-20 16:22 Priority: Minor Reporter: Craig Rodrigues If I navigate to: https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-1883/53/tests and click on line 6 of the logs, I cannot get a hyperlink to that line. However, if I go to https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-1883/53/pipeline I can get a direct hyperlink to a log line such as: https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-1883/53/pipeline#step-98-log-5 Add Comment
[JIRA] (JENKINS-24266) Test Results Analyzer plugin : Add hyperlink to the Test Results Analyzer report
Title: Message Title Craig Rodrigues updated JENKINS-24266 Fixed in https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-1883/53/tests Jenkins / JENKINS-24266 Test Results Analyzer plugin : Add hyperlink to the Test Results Analyzer report Change By: Craig Rodrigues Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Vivek Pandey commented on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Sometimes when stage is in progress, steps might not appear instantly because it might not yet be running so api serving them for the selected stage still be returning no steps. Regarding wrong status, Olivier Lamy Nicolae Pascu it might be api not returning correct status? I think there is existing issue with status of parallel stages, there might be ticket some where or may be its new one. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53125) Setting CookieManager causes issues with other plugins
Title: Message Title KaiHsiang Chang updated JENKINS-53125 Jenkins / JENKINS-53125 Setting CookieManager causes issues with other plugins Change By: KaiHsiang Chang Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/releases/tag/Parameterized-Remote-Trigger-3.0.5 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53125) Setting CookieManager causes issues with other plugins
Title: Message Title KaiHsiang Chang updated JENKINS-53125 Jenkins / JENKINS-53125 Setting CookieManager causes issues with other plugins Change By: KaiHsiang Chang Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Eric Lloyd commented on JENKINS-52661 Re: P4 Plugin fails to parse changelog I was also seeing this issue when running many parallel stages all doing checkouts. It seems like some of the stages start before the changlog.xml is fully generated. After the build finishes if I go on the master and check the changelog is correct. To fix this, for now, I had to move to only allow one stage to checkout at a time but that is less than Ideal. I am using P4 plugin version 1.8.14 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean)
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: View Parallel stages in the pipeline showing wrong statuses (In Blue Ocean) Vivek Pandey Yes indeed, when you click on the stage shown as Processing, the steps are not shown. As for the other processing stage shown wrongly as Passed, its steps are shown and can be selected. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title
jerry wiltse updated an issue
Jenkins / JENKINS-53140
Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Change By:
jerry wiltse
On a new Jenkins server, we're setting up new Jenkinsfiles from scratch. We're using parallel stages, which seems like it might be a factor based on searches for related issues. We have about 15 of these jobs with 4 parallel stages. For about 1 in 10 jobs, a stage will randomly fail in 1 second or less. If you hover over the stage it shows: {code:java}Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml{code}If you click the Stage Log it says: {code:java}No changes for since the previous build`{code}This can happen when the build is triggered by either of the following means: * From an upstream job * Manually by clicking "build now" Of note, we use SVN as our SCM with the following configuration:We use "Jenkinsfile from SCM", using URL like {code:java}http://myserver/myrepo/_automation{code}In the GUI, we do not configure SCM polling In the Jenkinsfile, we configure SCM polling, every 2 minutesIn the Jenkinsfile, we configure SCM checkout of {code:java}http://myserver/myrepo`|http://myserver/myrepo{code} The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . For each SCM polling period, the Subversion Polling Log show approximately multiple entries all at the same timestamp. These entries are some randomized mix of polling the two relevant URL's :{code:java}http://myserver/myrepo{code} and {code:java} http://myserver/myrepo/_automation{code}Interestingly, we've figured something out about these duplicate "Subversion Polling Entries" . There is 1 entry checking {code:java}http://myserver/myrepo/_automation{code} for changes for each stage in the build for the " . So, if we have 1 "Checkout Stage", 1 "Parallel Stages" block, and 3 "Parallel Stages", we see 5 total "Subversion Polling Entries" for {code:java}http://myserver/myrepo/_automation{code} . Not sure if this is by design or not. We have the latest versions of all plugins.
Add Comment
[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title
jerry wiltse updated an issue
Jenkins / JENKINS-53140
Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Change By:
jerry wiltse
On a new Jenkins server, we're setting up new Jenkinsfiles from scratch. We're using parallel stages, which seems like it might be a factor based on searches for related issues. We have about 15 of these jobs with 4 parallel stages. For about 1 in 10 jobs, a stage will randomly fail in 1 second or less. If you hover over the stage it shows: {code:java}Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml{code}If you click the Stage Log it says: {code:java}No changes for since the previous build`{code}This can happen when the build is triggered by either of the following means: * From an upstream job * Manually by clicking "build now" Of note, we use SVN as our SCM with the following configuration:We use "Jenkinsfile from SCM", using URL like {code:java}http://myserver/myrepo/_automation{code}In the GUI, we do not configure SCM polling In the Jenkinsfile, we configure SCM polling, every 2 minutesIn the Jenkinsfile, we configure SCM checkout of {code:java}http://myserver/myrepo`|http://myserver/myrepo{code} The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . For each SCM polling period, the Subversion Polling Log show approximately 4-8 multiple entries all at the same timestamp. These entries are some randomized mix of polling the two relevant URL's :{code:java}http://myserver/myrepo{code} and http://myserver/myrepo/_automation{code} Interestingly, we've figured something out about these duplicate "Subversion Polling Entries" . There is 1 for each stage in the build. So, if we have 1 "Checkout Stage", 1 "Parallel Stages" block, and 3 "Parallel Stages", we see 5 total "Subversion Polling Entries". Not sure if this is by design or not. We have the latest versions of all plugins.
Add Comment
[JIRA] (JENKINS-53140) Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Title: Message Title
jerry wiltse updated an issue
Jenkins / JENKINS-53140
Intermittent Random Stage Failures - No Changes Detected - Parallel Stages
Change By:
jerry wiltse
On a new Jenkins server, we're setting up new Jenkinsfiles from scratch. We're using parallel stages, which seems like it might be a factor based on searches for related issues. We have about 15 of these jobs with 4 parallel stages. For about 1 in 10 jobs, a stage will randomly fail in 1 second or less. If you hover over the stage it shows: {code:java} ` Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml ` {code} If you click the Stage Log it says: ` {code:java} No changes for since the previous build` {code} This can happen when the build is triggered by either of the following means: * From an upstream job * Manually by clicking "build now" Of note, we use SVN as our SCM with the following configuration:We use "Jenkinsfile from SCM", using URL like ` {code:java} http://myserver/myrepo/_automation ` {code} In the GUI, we do not configure SCM polling In the Jenkinsfile, we configure SCM polling, every 2 minutesIn the Jenkinsfile, we configure SCM checkout of `[ {code:java} http://myserver/myrepo`|http://myserver/myrepo ] {code} The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . For each SCM polling period, the Subversion Polling Log show approximately 4-8 entries all at the same timestamp. These entries are some randomized mix of polling the two relevant URL's : ` {code:java} http://myserver/myrepo ` {code} and ` http://myserver/myrepo/_automation ` {code} We have the latest versions of all plugins.
Add Comment
