[JIRA] (JENKINS-42486) pipeline utility zip doesn't preserve symlinks
Title: Message Title
aflat created an issue
Jenkins / JENKINS-42486
pipeline utility zip doesn't preserve symlinks
Issue Type:
Bug
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2017/Mar/05 3:45 AM
Environment:
jenkins: 2.40 pipeline-utility: 1.2.2
Priority:
Major
Reporter:
aflat
When using the zip task, symlinks are not preserved. The contents of the symlinks are copied in instead. dir("a_dir_with_symlinks_in_it"){ zip dir: '', glob: '', zipFile: "../my.zip" }
Add Comment
[JIRA] (JENKINS-42377) Add support for tokens from Token Macro Plugin
Title: Message Title Daniel Pfeiffer commented on JENKINS-42377 Re: Add support for tokens from Token Macro Plugin Opened pull request: https://github.com/jenkinsci/assembla-merge-request-builder-plugin/pull/6 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42377) Add support for tokens from Token Macro Plugin
Title: Message Title Daniel Pfeiffer started work on JENKINS-42377 Change By: Daniel Pfeiffer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37900) Support Assembly Informational Version
Title: Message Title Michael Fowler started work on JENKINS-37900 Change By: Michael Fowler Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37901) Assembly Version should be optional
Title: Message Title Michael Fowler started work on JENKINS-37901 Change By: Michael Fowler Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37900) Support Assembly Informational Version
Title: Message Title Michael Fowler assigned an issue to Michael Fowler Jenkins / JENKINS-37900 Support Assembly Informational Version Change By: Michael Fowler Assignee: Sanketh PB Michael Fowler Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37901) Assembly Version should be optional
Title: Message Title Michael Fowler assigned an issue to Michael Fowler Jenkins / JENKINS-37901 Assembly Version should be optional Change By: Michael Fowler Assignee: Sanketh PB Michael Fowler Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41804) Jenkins.instance.getItem does not find jobs, in a Thread launched from a systemGroovyScript
Title: Message Title Jon Alberdi commented on JENKINS-41804 Re: Jenkins.instance.getItem does not find jobs, in a Thread launched from a systemGroovyScript We indeed agree on the inconsistency of the API. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Mark Waite commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use Special thanks to Matt Hauck for the initial implementation and to creste for the final implementation and adaptations as needed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title JP Lemelin commented on JENKINS-38447 Re: Bitbucket hooks don't work for Pipeline jobs If you want to use a Pipeline with Bitbucket and Pull Request, just use multibranch project with Bitbucket Branch Source plugin It really simple to setup: https://jenkins.io/doc/book/pipeline/multibranch/ Plugin: https://plugins.jenkins.io/cloudbees-bitbucket-branch-source Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Alex Agranov commented on JENKINS-30318 Re: Git plugin breaks usage of Git LFS due to lack of Git Clone use Just tested, after adding "Git LFS Pull After Checkout" as an Additional Behavior, and works like a charm! You. Da. Man. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40385) Github Issue plugin refuses to create issue on build failure
Title: Message Title Daniel Lo Nigro resolved as Fixed This was fixed in version 1.2.2 of the plugin. Jenkins / JENKINS-40385 Github Issue plugin refuses to create issue on build failure Change By: Daniel Lo Nigro Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. 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-42482) Optional settings (like issueTitle, issueBody) are not optional in Job DSL
Title: Message Title Daniel Lo Nigro resolved as Fixed This was fixed in version 1.2.2 of the plugin. Jenkins / JENKINS-42482 Optional settings (like issueTitle, issueBody) are not optional in Job DSL Change By: Daniel Lo Nigro Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. 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-40385) Github Issue plugin refuses to create issue on build failure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40385 Re: Github Issue plugin refuses to create issue on build failure Code changed in jenkins User: Daniel Lo Nigro Path: src/main/java/org/jenkinsci/plugins/githubissues/GitHubIssueNotifier.java http://jenkins-ci.org/commit/github-issues-plugin/32aea3f6f0971d3c9976a7fc58a75be1e679d619 Log: Fix JENKINS-40385: Use AbstractBuild rather than Build so it works for Maven builds too Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42482) Optional settings (like issueTitle, issueBody) are not optional in Job DSL
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42482 Re: Optional settings (like issueTitle, issueBody) are not optional in Job DSL Code changed in jenkins User: Daniel Lo Nigro Path: src/dev/assets/work/jobs/test_jobdsl_seed/config.xml src/main/java/org/jenkinsci/plugins/githubissues/GitHubIssueNotifier.java http://jenkins-ci.org/commit/github-issues-plugin/2c2dd133d3e5009f24b630a6ea53ba58e5035d2a Log: Fix JENKINS-42482: Move properties from DataBoundConstructor to DataBoundSetter so that Job DSL treats them as optional References https://github.com/jenkinsci/slack-plugin/pull/236 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title Alvaro Lobato commented on JENKINS-42484 Re: JAVA_TOOL_OPTIONS message displayed when using with maven I had a look at the changes made to fix JENKINS-42179 and you had it as arguments to the command line before using JAVA_TOOL_OPTIONS, did you try MAVEN_OPT? If not I can give it a shot. We could also try the new extension mechanism or the jvm.config but only for mvn +3.3, but we could fallback for old versions http://blog.soebes.de/blog/2015/03/17/apache-maven-3-dot-3-1-features/ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41804) Jenkins.instance.getItem does not find jobs, in a Thread launched from a systemGroovyScript
Title: Message Title Daniel Beck commented on JENKINS-41804 Re: Jenkins.instance.getItem does not find jobs, in a Thread launched from a systemGroovyScript there might still be a bug There is not. http://javadoc.jenkins-ci.org/jenkins/model/Jenkins.html#getItem%28java.lang.String%29 Returns:an item whose Item.getName() is name and whose Item.getParent() is this, or null if there is no such item, or there is but the current user lacks both Item.DISCOVER and Item.READ on it http://javadoc.jenkins-ci.org/jenkins/model/Jenkins.html#getItemMap%28%29 Returns the read-only view of all the TopLevelItems keyed by their names. This method is efficient, as it doesn't involve any copying. It's a bit inconsistent which methods apply permission checks and which don't if they're not exposed to the UI, but both of these behave as documented. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you 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-41804) Jenkins.instance.getItem does not find jobs, in a Thread launched from a systemGroovyScript
Title: Message Title
Jon Alberdi commented on JENKINS-41804
Re: Jenkins.instance.getItem does not find jobs, in a Thread launched from a systemGroovyScript
Let me reformulate:
if authentication is required to get read access to a job, there might still be a bug, as
we can anonymously get that job, through
getItemMap()['job'] instead of using
getItem('job')
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title Alvaro Lobato commented on JENKINS-42484 Re: JAVA_TOOL_OPTIONS message displayed when using with maven Ok, I missed that original issue. Feel free to close this or leave it as a reminder. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30873) Jenkins' Git plugin reparses all previous build.xml on restart
Title: Message Title Mark Waite commented on JENKINS-30873 Re: Jenkins' Git plugin reparses all previous build.xml on restart A warning is logged by git plugin 3.1.0 (released on 4 Mar 2017) when many BuildData instances are attached to a build/ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42236) SCMEventImpl should check isMatch() conditions in heads() method
Title: Message Title Mark Waite updated JENKINS-42236 Git plugin 3.1.0 released on 4 Mar 2017 includes this change. Jenkins / JENKINS-42236 SCMEventImpl should check isMatch() conditions in heads() method Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. 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-42050) How to set multiple git refspec in checkout step?
Title: Message Title Mark Waite commented on JENKINS-42050 Re: How to set multiple git refspec in checkout step? Help was added in Git plugin 3.1.0 released on 4 Mar 2017. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
Title: Message Title Mark Waite commented on JENKINS-19022 Re: GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields A warning is reported to the log by git plugin 3.1.0 released 4 Mar 2017. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42204) Scan of git pipeline fails with NPE due to recent GitSCMSource change
Title: Message Title Mark Waite commented on JENKINS-42204 Re: Scan of git pipeline fails with NPE due to recent GitSCMSource change Git plugin 3.1.0 released on 4 Mar 2017 includes this fix. This bug never existed in any released version of the plugin, only in pre-releases. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40908) GitSCMSource: support custom remote and refspec
Title: Message Title Mark Waite closed an issue as Fixed Included in git plugin 3.1.0 released 4 Mar 2017 Jenkins / JENKINS-40908 GitSCMSource: support custom remote and refspec Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38708) git checkout is run without credentials
Title: Message Title Mark Waite resolved as Fixed Git plugin 3.1.0 released on 4 Mar 2017 now includes support for command line git large file support. Git checkout does not run with credentials, rather an additional step has been added which will perform an authenticated git lfs pull Jenkins / JENKINS-38708 git checkout is run without credentials Change By: Mark Waite Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-40174) Missing authentication during git checkout and git-lfs
Title: Message Title Mark Waite resolved as Fixed Git plugin 3.1.0 released on 4 Mar 2017 now includes support for command line git large file support. Jenkins / JENKINS-40174 Missing authentication during git checkout and git-lfs Change By: Mark Waite Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-30318) Git plugin breaks usage of Git LFS due to lack of Git Clone use
Title: Message Title Mark Waite resolved as Fixed Git plugin 3.1.0 released on 4 Mar 2017 now includes support for command line git large file support. Jenkins / JENKINS-30318 Git plugin breaks usage of Git LFS due to lack of Git Clone use Change By: Mark Waite Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you 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-35687) Add explicit support for git lfs
Title: Message Title Mark Waite resolved as Fixed Git plugin 3.1.0 released on 4 Mar 2017 now includes support for command line git large file support. Jenkins / JENKINS-35687 Add explicit support for git lfs Change By: Mark Waite Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-42483) Certain GDSL methods are not generated
Title: Message Title
Hoshang Sadiq updated an issue
Jenkins / JENKINS-42483
Certain GDSL methods are not generated
Change By:
Hoshang Sadiq
When using the pipeline syntax gdsl generator, certain methods are not generated and others are not generated correctly (as far as I can tell anyway). The ones I noticed are {{podTemplate}}'s namedParam {{containers}} should be a {{List}} rather than a {{Map}}. Additionally, it doesn't generate a method for {{containerTemplate}}, {{podAnnotation}}, {{hostPathVolume}}.Additional errors being reported by IntelliJ:{code}checkout scm{code} Error reported > bq. 'checkout' cannot be applied to '(org.jenkinsci.plugins.workflow.multibranch.SCMVar)'
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-42484
Re: JAVA_TOOL_OPTIONS message displayed when using with maven
"{{JAVA_TOOL_OPTIONS}}" is the only solution I found to pass " {{ -Dmaven.ext.class.path=... }} " to the subsequent Maven build when invoking "mvn release:prepare release:perform". See JENKINS-42179 . We could see with the Maven project if they could use an environment variable in addition to the system property "{{-Dmaven.ext.class.path=...}}". > and it certain cases picked up as a Javadoc warningI think that it is picked as a "warning" because it is outputted by the JVM in "{{stderr}}" and not in "{{stdout}}". I don't think that it is related to javadocs. It seems to appear in the log message you mention because "{{javadoc:javadoc}}" does a fork of the JVM to launch the javadoc tool ["{{javadoc:javadoc-no-fork}}|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html].I see the same "{{JAVA_TOOL_OPTIONS}}" message with the FindBugs plugins that spawns a new process.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-42484
Re: JAVA_TOOL_OPTIONS message displayed when using with maven
"{{ JAVA_TOOL_OPTIONS }}" is the only solution I found to pass "-Dmaven.ext.class.path=..." to the subsequent Maven build when invoking "mvn release:prepare release:perform". See JENKINS-42179> and it certain cases picked up as a Javadoc warning:I think that it is picked as a "warning" because it is outputted by the JVM in "{{stderr}}" and not in "{{stdout}}". I don't think that it is related to javadocs. It seems to appear in the log message you mention because "{{javadoc:javadoc}}" does a fork of the JVM to launch the javadoc tool ["{{javadoc:javadoc-no-fork}}|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html].I see the same message with the FindBugs plugins that spawns a new process.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-42484
Re: JAVA_TOOL_OPTIONS message displayed when using with maven
"{{JAVA_TOOL_OPTIONS}}" is the only solution I found to pass "-Dmaven.ext.class.path=..." to the subsequent Maven build when invoking "mvn release:prepare release:perform". See JENKINS-42179> and it certain cases picked up as a Javadoc warning : I think that it is picked as a "warning" because it is outputted by the JVM in "{{stderr}}" and not in "{{stdout}}". I don't think that it is related to javadocs. It seems to appear in the log message you mention because "{{javadoc:javadoc}}" does a fork of the JVM to launch the javadoc tool ["{{javadoc:javadoc-no-fork}}|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html].I see the same message with the FindBugs plugins that spawns a new process.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-42484
Re: JAVA_TOOL_OPTIONS message displayed when using with maven
"{{JAVA_TOOL_OPTIONS}}" is the only solution I found to pass "-Dmaven.ext.class.path=..." to the subsequent Maven build when invoking "mvn release:prepare release:perform". See JENKINS-42179> and it certain cases picked up as a Javadoc warningI think that it is picked as a "warning" because it is outputted by the JVM in "{{stderr}}" and not in "{{stdout}}". I don't think that it is related to javadocs. It seems to appear in the log message you mention because "{{javadoc:javadoc}}" does a fork of the JVM to launch the javadoc tool ["{{javadoc:javadoc-no-fork}}|https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html].I see the same "{{JAVA_TOOL_OPTIONS}}" message with the FindBugs plugins that spawns a new process.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title Cyrille Le Clerc commented on JENKINS-42484 Re: JAVA_TOOL_OPTIONS message displayed when using with maven JAVA_TOOL_OPTIONS is the only solution I found to pass "-Dmaven.ext.class.path=..." to the subsequent Maven build when invoking "mvn release:prepare release:perform". See JENKINS-42179 > and it certain cases picked up as a Javadoc warning: I think that it is picked as a "warning" because it is outputted by the JVM in "stderr" and not in "stdout". I don't think that it is related to javadocs. It seems to appear in the log message you mention because "javadoc:javadoc" does a fork of the JVM to launch the javadoc tool "javadoc:javadoc-no-fork. I see the same message with the FindBugs plugins that spawns a new process. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-42484 JAVA_TOOL_OPTIONS message displayed when using with maven Change By: Cyrille Le Clerc Summary: ToolOption JAVA_TOOL_OPTIONS message displayed when using with maven Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42485) 404 when clicking on the configure wheel of a (pipeline) job
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-42485 404 when clicking on the configure wheel of a (pipeline) job Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/04 2:54 PM Environment: Jenkins 2.32.3 Blue Ocean 1.0.0-b24 Priority: Major Reporter: Baptiste Mathus Steps to reproduce: Start a fresh Jenkins 2.32.3 Install latest BO 1.0.0-b24 Create a Pipeline (even empty) Click on the configure cogwheel => 404 It seems like it incorrectly prepends the root URL with /jenkins Jenkins is indeed running on http://localhost:8080 and clicking on the wheel leads to http://localhost:8081/jenkins/job/pipeline/configure Can provide more details and/or a screencast if you cannot reproduce for whatever reason.
[JIRA] (JENKINS-42485) 404 when clicking on the configure wheel of a (pipeline) job
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-42485 404 when clicking on the configure wheel of a (pipeline) job Change By: Baptiste Mathus Steps to reproduce:* Start a fresh Jenkins 2.32.3* Install latest BO 1.0.0-b24* Create a Pipeline (even empty)* Click on the configure cogwheel=> 404It seems like it incorrectly prepends the root URL with /jenkins (reminds me of a similar issue like 6 months ago, going to search for it) Jenkins is indeed running on http://localhost:8080 and clicking on the wheel leads to http://localhost:8081/jenkins/job/pipeline/configureCan provide more details and/or a screencast if you cannot reproduce for whatever reason. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-42485) 404 when clicking on the configure wheel of a (pipeline) job
Title: Message Title Baptiste Mathus closed an issue as Duplicate Jenkins / JENKINS-42485 404 when clicking on the configure wheel of a (pipeline) job Change By: Baptiste Mathus Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42485) 404 when clicking on the configure wheel of a (pipeline) job
Title: Message Title Baptiste Mathus commented on JENKINS-42485 Re: 404 when clicking on the configure wheel of a (pipeline) job OK apparently I just filed a dupe of JENKINS-42291 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42484) JAVA_TOOL_OPTIONS message displayed when using with maven
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-42484 JAVA_TOOL_OPTIONS message displayed when using with maven Change By: Cyrille Le Clerc Summary: ToolOption JAVA_TOOL_OPTIONS message displayed when using with maven Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42485) 404 when clicking on the configure wheel of a (pipeline) job
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-42485 404 when clicking on the configure wheel of a (pipeline) job Change By: Baptiste Mathus Steps to reproduce:* Start a fresh Jenkins 2.32.3* Install latest BO 1.0.0-b24* Create a Pipeline (even empty)* Click on the configure cogwheel=> 404It seems like it incorrectly prepends the root URL with /jenkins (reminds me of a similar issue like 6 months ago, going to search for it) Jenkins is indeed running on http://localhost:8080 and clicking on the wheel leads to http://localhost:8081/jenkins/job/pipeline/configureCan provide more details and/or a screencast if you cannot reproduce for whatever reason. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-42485) 404 when clicking on the configure wheel of a (pipeline) job
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-42485 404 when clicking on the configure wheel of a (pipeline) job Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/04 2:54 PM Environment: Jenkins 2.32.3 Blue Ocean 1.0.0-b24 Priority: Major Reporter: Baptiste Mathus Steps to reproduce: Start a fresh Jenkins 2.32.3 Install latest BO 1.0.0-b24 Create a Pipeline (even empty) Click on the configure cogwheel => 404 It seems like it incorrectly prepends the root URL with /jenkins Jenkins is indeed running on http://localhost:8080 and clicking on the wheel leads to http://localhost:8081/jenkins/job/pipeline/configure Can provide more details and/or a screencast if you cannot reproduce for whatever reason.
[JIRA] (JENKINS-32441) SEVERE: Failed Loading plugin monitoring
Title: Message Title evernat commented on JENKINS-32441 Re: SEVERE: Failed Loading plugin monitoring Nelu Vasilica Any news? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I think getting and storing an OAuth token is desirable on login. This is how (for example) iPhone apps work. This could have other uses, such as using that token for Replays (instead of the Org token). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I think getting and storing an OAuth token is desirable on login. This is how (for example) iPhone apps work. This could have other uses, such as using that token for Replays (instead of the Org token). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I think getting and storing an OAuth token is desirable on login. This is how (for example) iPhone apps work. This could have other uses, such as using that token for Replays (instead of the Org token). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well I think getting and storing an OAuth token is desirable on login. This is how (for example) iPhone apps work. This could have other uses, such as using that token for Replays (instead of the Org token). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well Oh! I understand now. It also explains the permissions problem I was having with the Jenkins CLI when I discovered JENKINS-42421 That being said, there are other uses for the SSH public keys, including the Jenkins-hosted git server for the workflow pipeline, etc. So this may still be useful. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well Oh! I understand now. It also explains the permissions problem I was having with the Jenkins CLI when I discovered JENKINS-42421 That being said, there are other uses for the SSH public keys, including the Jenkins-hosted git server for the workflow pipeline, etc. So this may still be useful. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34649) Get ssh public keys from github as well
Title: Message Title Christian Höltje commented on JENKINS-34649 Re: Get ssh public keys from github as well Oh! I understand now. It also explains the permissions problem I was having with the Jenkins CLI when I discovered JENKINS-42421 That being said, there are other uses for the SSH public keys, including the Jenkins-hosted git server for the workflow pipeline, etc. So this may still be useful. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42421) BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985'
Title: Message Title Christian Höltje commented on JENKINS-42421 Re: BROKEN: Team names/slugs show up as 'org.kohsuke.github.GHTeam@e004985' Huh. I didn't know about /whoAmI Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35028) Execute shell textarea overflow
Title: Message Title Oleg Nenashev resolved as Duplicate Duplicates JENKINS-27367, which has been fixed in 2.26 and then backported to 2.19.4 Jenkins / JENKINS-35028 Execute shell textarea overflow Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-34530) Jenkins test harness does not support Jenkins 2.x
Title: Message Title Tomas Bjerre commented on JENKINS-34530 Re: Jenkins test harness does not support Jenkins 2.x Vegard Endresen I also encountered this. I changed test-harness to latest version, and that works. Now I have: org.jenkins-ci.plugins plugin 2.23 2.0 1.115 2.19 false Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title Gunter Grodotzki commented on JENKINS-38126 Re: Credentials dropdown empty on git scm Matt Wilson, I owe you a beer! This was exactly the reason for our problems as well. I switched "Project default Build Authorization" to "Run as User who Triggered Build", which fixes the problem of the git-creds dropdown, but for that I am now getting the following warnings on downstream builds: 09:24:01 Warning: this build has no associated authentication, so build permissions may be lacking, and downstream projects which cannot even be seen by an anonymous user will be silently skipped Downstream jobs still seem to be triggered, but they are not anymore directly linked within the console-output. To me the security setup of Jenkins does not fully make sense: why can downstream jobs just not assume the user that triggered the upstream job? why can there not be a "special" user that can be used for scm-polling/trigger/timer? Some documentations suggest SYSTEM is anonymous? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42484) ToolOption message displayed when using with maven
Title: Message Title Alvaro Lobato created an issue Jenkins / JENKINS-42484 ToolOption message displayed when using with maven Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2017/Mar/04 8:48 AM Priority: Minor Reporter: Alvaro Lobato ToolOption message displayed when using with maven, and it certain cases picked up as a Java doc warning: 08:38:00 - withMaven Wrapper script - 08:38:00 Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven0cc64df6/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven0cc64df6" 08:38:00 Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00) 08:39:44 [INFO] <<< maven-javadoc-plugin:2.10.1:javadoc (default) < generate-sources @ operations-center-client <<< 08:39:44 [INFO] 08:39:44 [INFO] --- maven-javadoc-plugin:2.10.1:javadoc (default) @ operations-center-client --- 08:39:47 [INFO] 08:39:47 2 warnings 08:39:47 [WARNING] Javadoc Warnings 08:39:47 [WARNING] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven0ba4a79a/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven0ba4a79a" 08:39:47 [WARNING]
[JIRA] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29922 Re: Promote delegates of metasteps to top-level functions, deprecate $class Code changed in jenkins User: Suresh Kumar P Path: pom.xml src/main/java/sp/sd/fileoperations/FileCopyOperation.java src/main/java/sp/sd/fileoperations/FileCreateOperation.java src/main/java/sp/sd/fileoperations/FileDeleteOperation.java src/main/java/sp/sd/fileoperations/FileDownloadOperation.java src/main/java/sp/sd/fileoperations/FileJoinOperation.java src/main/java/sp/sd/fileoperations/FileOperationsBuilder.java src/main/java/sp/sd/fileoperations/FilePropertiesToJsonOperation.java src/main/java/sp/sd/fileoperations/FileTransformOperation.java src/main/java/sp/sd/fileoperations/FileUnTarOperation.java src/main/java/sp/sd/fileoperations/FileUnZipOperation.java src/main/java/sp/sd/fileoperations/FolderCopyOperation.java src/main/java/sp/sd/fileoperations/FolderCreateOperation.java src/main/java/sp/sd/fileoperations/FolderDeleteOperation.java http://jenkins-ci.org/commit/file-operations-plugin/e0b44fcd8484372deef5a22e4daa048b4b5e8f46 Log: Added Symbols for Jenkins Pipeline support JENKINS-29922 $class must die Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42481) NPE when cancelling a on a withMaven step
Title: Message Title
Alvaro Lobato commented on JENKINS-42481
Re: NPE when cancelling a on a withMaven step
When canceled this error is always displayed:
[Pipeline] }
08:37:23 ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /home/user/workspace/Tinkering/alvaro/Jenkinsfile-test@tmp/withMaven2f9f6307/maven-spy-20170304-083657-567.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org
Maybe a cancel should be detected and logs not processed. From global logs
Mar 04, 2017 8:38:55 AM WARNING org.jenkinsci.plugins.pipeline.maven.reporters.GeneratedArtifactsReporter listArtifacts
listArtifacts: Project MavenArtifact{com.cloudbees.operations-center.client:operations-center-client::2.32.0.4-SNAPSHOT}: no associated file found for MavenArtifact{com.cloudbees.operations-center.client:operations-center-client:hpi:2.32.0.4-SNAPSHOT} in "1.0" encoding="UTF-8"?>"operations-center-client" extension="hpi" groupId="com.cloudbees.operations-center.client" id="com.cloudbees.operations-center.client:operations-center-client:hpi:2.32.0.4-SNAPSHOT" type="hpi" version="2.32.0.4-SNAPSHOT">
Add Comment
[JIRA] (JENKINS-42483) Certain GDSL methods are not generated
Title: Message Title Hoshang Sadiq created an issue Jenkins / JENKINS-42483 Certain GDSL methods are not generated Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin, workflow-aggregator-plugin Created: 2017/Mar/04 8:11 AM Priority: Minor Reporter: Hoshang Sadiq When using the pipeline syntax gdsl generator, certain methods are not generated and others are not generated correctly (as far as I can tell anyway). The ones I noticed are podTemplate's namedParam containers should be a List rather than a Map. Additionally, it doesn't generate a method for containerTemplate, podAnnotation, hostPathVolume. Additional errors being reported by IntelliJ: checkout scm > 'checkout' cannot be applied to '(org.jenkinsci.plugins.workflow.multibranch.SCMVar)' Add Comment
[JIRA] (JENKINS-40768) Jenkins client-side HTML5 storage API
Title: Message Title Tom FENNELLY resolved as Done Jenkins / JENKINS-40768 Jenkins client-side HTML5 storage API Change By: Tom FENNELLY Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40768) Jenkins client-side HTML5 storage API
Title: Message Title James Dumay stopped work on JENKINS-40768 Change By: James Dumay Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39657) Chrome Dev Tools Extension for Blue Ocean
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39657 Chrome Dev Tools Extension for Blue Ocean Change By: James Dumay Sprint: 1. 1 0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
