[JIRA] (JENKINS-37400) Symbols for constants variables in workflow-cps
Title: Message Title ikedam commented on JENKINS-37400 Re: Symbols for constants variables in workflow-cps And now I'm facing a problem: this implementation doesn't work when the script is sandboxed. The sandbox cannot decide the property is whitelisted and doesn't pass to CpsScript. Script-security looks handle properties and methods in different ways. Though it calls receiver.invokeMethod for methods, it calls not receiver.getProperty but receiver.getBinding().getVarialbe for properties. It might work by calling receiver.getProperty instead, but I'm not sure it doesn't break the security model of script-security. 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-37400) Symbols for constants variables in workflow-cps
Title: Message Title ikedam commented on JENKINS-37400 Re: Symbols for constants variables in workflow-cps I think this can be implemented in this way: * Define UninstantiatedConstant in struct-plugin just like UninstantiatedDescribable. Implement DSL#getProperty in workflow-cps plugin, and call from CpsScript#getProperty for unknown properties. Create an instance of UninstantiatedConstant for those unknown properties. I don't know what type is required for that property at that time and can't determine the value for the property. The required type is determined when a describable object is instantiated and I can determine the value for the property. So wrap the property with UninstantiatedConstant and leave it for lazy evaluation. Determine the value for the unknown property when evaluating DescribableModel#coerce Throw MissingPropertyException if the value cannot be determined. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37400) Symbols for constants variables in workflow-cps
Title: Message Title
ikedam created an issue
Jenkins / JENKINS-37400
Symbols for constants variables in workflow-cps
Issue Type:
New Feature
Assignee:
ikedam
Components:
structs-plugin, workflow-plugin
Created:
2016/Aug/14 4:39 AM
Priority:
Minor
Reporter:
ikedam
I want to use enum names for parameters of steps in pipeline jobs like:
def runWrapper = selectRun job: 'upstream-project-name',
selector: status(Successful)
Successful is an enum value. I believe workflow-cps can determine what Successful means as the type of status is required to be an enum type. Background: Run selector plugin is working to introduce {{@Symbol}}s: https://github.com/jenkinsci/run-selector-plugin/pull/14 It allows scripts use run-selector like this:
def runWrapper = selectRun job: 'upstream-project-name',
selector: status('Successful')
'Successful' will be resolved to BuildStatus.Successful with Enum.valueOf (BuildStatus is an enum type). But other selectors in run-selector often expects strings starting with lower-case letters. For example, PermalinkRunSelector expects "lastSuccessful". This causes inconsistencies of usages of selectors and should be confusing for users. On the other hands, allowing "successlful" for parameters of status means to define enum values with lower-case letters like BuildStatus.successlful. It is strange as Java code. I think this can be resolved by either
[JIRA] (JENKINS-37399) Choices from Choice parameter aren't populated
Title: Message Title kenorb created an issue Jenkins / JENKINS-37399 Choices from Choice parameter aren't populated Issue Type: Bug Assignee: Joel Johnson Components: ez-templates-plugin Created: 2016/Aug/14 1:46 AM Environment: Jenkins ver. 2.7.1, EZ Templates 1.2.0 Priority: Minor Reporter: kenorb My template job consist Choice parameter and when Choices are updated (e.g. I'm adding new choice items), the Choices in job which implements that template aren't updated (it says the same as it was). It works for other type of parameters, so it sounds like it's Choice parameter specific. Add Comment
[JIRA] (JENKINS-36438) Naginator plugin throws NPE for pipeline jobs
Title: Message Title ikedam resolved as Fixed Fixed in naginator-1.17.2. It will be available in the update center in a day. "Retry" link is no longer displayed for pipeline builds as naginator-plugin doesn't support them for now. Jenkins / JENKINS-36438 Naginator plugin throws NPE for pipeline jobs Change By: ikedam Status: In Progress Resolved Assignee: ikedam Anna Kordas Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37391) Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Title: Message Title
Mark Waite commented on JENKINS-37391
Re: Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Thanks for the additional info. Given that info, I'm accepting the pull request "as is", with "git" and "jgit". Those are the most "natural" names for me since those are the argument values for the `Git.with(String)` call, and are the common terms used to refer to the two different implementations throughout the source code.
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-37398) unclassified field groovy.util.Node xxx
Title: Message Title
Daniel Sobral created an issue
Jenkins / JENKINS-37398
unclassified field groovy.util.Node xxx
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
script-security-plugin
Created:
2016/Aug/13 10:36 PM
Priority:
Minor
Reporter:
Daniel Sobral
I'm trying to use one of Groovy's XML libraries, but I keep stumbling on errors. XMLSlurper gives me an Object getProperty String which I'm not supposed to accept. When I use XMLParser, I get this:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field groovy.util.Node testcase
This one does not appear on approval list. It comes from this piece of code:
def result = new XmlParser().parseText(xml)
result.testcase.'*'.findAll { node -> node.name() == 'failure' || node.name() == 'error' }*.text()
Using result['testcase'] gets me past this error, up to '*', which I haven't tried using the map syntax for yet. Still, it doesn't appear on the security list for approval/denial.
[JIRA] (JENKINS-37397) Allow tool step to use Symbol names instead of classes for tool types
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37397 Allow tool step to use Symbol names instead of classes for tool types Issue Type: Improvement Assignee: Andrew Bayer Components: workflow-plugin Created: 2016/Aug/13 10:33 PM Priority: Minor Reporter: Andrew Bayer Related to JENKINS-37836 - now that we're getting @Symbol on ToolDescriptor, it makes sense to change the tool step to take either the descriptor ID (i.e., the class name) or the relevant symbol. Add Comment
[JIRA] (JENKINS-29977) Git Plugin truncates changelog
Title: Message Title Mark Waite edited a comment on JENKINS-29977 Re: Git Plugin truncates changelog [~warden] I'm not sure how the Jira plugin requests the commit messages. It seems (from [~gkilleen]'s [description|https://issues.jenkins-ci.org/browse/JENKINS-29977?focusedCommentId=266766=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-266766]) that the Jira plugin is reading the trimmed form of the commit messages as they are presented in the user interface, instead of using the git client plugin methods to collect the commit message from the git repository.How does the Jira plugin request the commit messages?The git client plugin (which provides API access to git repositories) provides various "changelog" methods which return changelog entries for ranges of commits. As far as I know, those API calls don't truncate. The truncation happens (as far as I recall) in the git plugin layer prior to presentation in the user interface. The git plugin provides a user interface (recent changes list, links to source repositories, etc.) and workflow elements (submodule support, sparse checkout configuration, tagging, pushing commits back to the remote repository, etc.) 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-37396) java.io.NotSerializableException: groovy.sql.GroovyRowResult
Title: Message Title Joe Roberts commented on JENKINS-37396 Re: java.io.NotSerializableException: groovy.sql.GroovyRowResult java.io.NotSerializableException: groovy.sql.GroovyRowResult at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:569) at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65) at org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56) at org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50) at org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344) at java.util.HashMap.internalWriteEntries(HashMap.java:1785) at java.util.HashMap.writeObject(HashMap.java:1362) at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:271) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:976) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at
[JIRA] (JENKINS-29977) Git Plugin truncates changelog
Title: Message Title Mark Waite commented on JENKINS-29977 Re: Git Plugin truncates changelog Radek Antoniuk I'm not sure how the Jira plugin requests the commit messages. It seems (from Gerald Killeen's description) that the Jira plugin is reading the trimmed form of the commit messages as they are presented in the user interface, instead of using the git client plugin methods to collect the commit message from the git repository. How does the Jira plugin request the commit messages? The git client plugin (which provides API access to git repositories) provides various "changelog" methods which return changelog entries for ranges of commits. As far as I know, those API calls don't truncate. The truncation happens (as far as I recall) in the git plugin layer prior to presentation in the user interface. 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-37396) java.io.NotSerializableException: groovy.sql.GroovyRowResult
Title: Message Title
Joe Roberts created an issue
Jenkins / JENKINS-37396
java.io.NotSerializableException: groovy.sql.GroovyRowResult
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2016/Aug/13 10:13 PM
Environment:
Centos 7 (3.10.0-327.22.2.el7.x86_64) openjdk version "1.8.0_101" OpenJDK Runtime Environment (build 1.8.0_101-b13) OpenJDK 64-Bit Server VM (build 25.101-b13, mixed mode) Jenkins 2.17 Job DSL plugin 1.48
Priority:
Blocker
Reporter:
Joe Roberts
When querying a MySQL database to perform functions on the resulting GroovyRowResults, I receive a NotSerializableException when attempting to use a string value from a GroovyRowResult in a "sh" call. In my worflow library:
def mergeEmtTag(tag){
stage 'Connect to database'
def db = [url:'jdbc:mysql://localhost:3306/jenkins', user:'jenkins_user', password:'xx', driver:'com.mysql.jdbc.Driver']
def sql = Sql.newInstance(db.url, db.user, db.password, db.driver)
stage 'Retrieve all EMTs'
def rows = sql.rows("SELECT * FROM emts")
sql.close()
for ( i in rows ) {
sh """
if [ -d "${i.slug}" ]; then
mkdir "${i.slug}"
fi
"""
dir("${slug}"){
sh """
git clone "g...@bitbucket.org:/${row.slug}.git" .
cd $slug
git remote add upstream g...@bitbucket.org:xxx/emt-master.git
git checkout origin/master
git fetch --tags upstream
git merge "${tag}"
if [ \$? -ne 0 ]; then
[JIRA] (JENKINS-32560) jira-plugin generating message in the wrong ticket
Title: Message Title Radek Antoniuk commented on JENKINS-32560 Re: jira-plugin generating message in the wrong ticket Is this possible that there were concurrent builds running on the same jenkins slave when this happened? 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-29977) Git Plugin truncates changelog
Title: Message Title Radek Antoniuk commented on JENKINS-29977 Re: Git Plugin truncates changelog I'm quite surprised with the discussion and approach on this. I'm maintaining the jira-plugin and as mentioned earlier, it depends on parsing the commit message. The commit message is an integral part of a commit and should not be arbitrarily consumed by a plugin which role is to be an interface to git repository. References to github web UI or gitweb (again, web UI) are wrong as the purpose of those web UIs are different than a plugin that is a git provider. 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-37391) Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Title: Message Title
Andrew Bayer commented on JENKINS-37391
Re: Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
The @Symbol annotation's reasoning and behavior is described over at the structs plugin wiki page. The allowed values are, well, any string, scoped to the ExtensionPoint in question. Right now, the only ToolDescriptor with the @Symbol annotation are JDK and MavenInstallation in core. I'd like to add this to more tools to do a couple things:
Simplify the tool step in Pipeline by allowing you to specify the tool type without needing to give the ToolDescriptor class name - i.e., right now, if you want to be specific and not just specify the install name, you need to do tool name: 'maven3.3.9', type: 'hudson.tasks.Maven$MavenInstallation' (yeah, in this case, there's no ambiguity, but you know what I'm getting at. =) ), and with the @Symbol on all ToolDescriptor, I'll be able to change the tool step to allow tool name: 'maven3.3.9', type: 'maven', etc...
I've got a project that'll be coming to the jenkinsci org in the next couple weeks that provides a more config-like way to define your Pipelines, and having the @Symbol on tools will make my tools section much, much cleaner.
and in general, there's been a trend towards trying to get @Symbol on Extension uses to open up more DSL possibilities down the road and get rid of more and more of the ugly [$class: 'Foo', arg1: ...] syntax needed for some things now.
There are basically no risks to this at all. As I said, the scoping for the @Symbol values is by ExtensionPoint, so we can have multiple uses of the same name as long as they're on different ExtensionPoint - see the build step descriptor and the tool descriptor for Maven, for example. All this does is add some discoverable metadata to the descriptors. As I mentioned over on the PR, I'm completely flexible on the naming - I just went with my default mentality, where GitTool proper would line up with git as a name, and JGitTool would get jgit as a name.
Add Comment
[JIRA] (JENKINS-37391) Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Title: Message Title
Mark Waite commented on JENKINS-37391
Re: Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
I don't object to this, but I don't understand who benefits by it, how they benefit, or the impact of the addition. Some sample questions:
Who does this help?
How does it help them?
What are the risks from the change?
Where are the allowed `@Symbol` values described and how are they used? For example, today there is a "Default" implementation (which is command line git) and an optional "jgit" implementation which the administrator can add, then can use from within jobs
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-33166) Problem with settings validation
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-33166 Problem with settings validation Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35998) No issue update if at least one issue does not exists
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-35998
No issue update if at least one issue does not exists
Change By:
Radek Antoniuk
If an issue does not exist in JIRA, all other issues in build will not get an update.JIRA issues won't be saved either!I am using Plugin-Version 2.2.1Build Log: {noformat} Checking out Revision 7a9b0232458eea8717a61bbb90bf93d7d0d8f815 (refs/remotes/origin/v18.00/feature/IssueUpdate)Error updating JIRA issues. Saving issues for next build.java.lang.NullPointerException {noformat} Jenkins-Log: {noformat} Jun 16, 2016 9:00:39 AM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotateAnnotating JIRA id: 'PD-882099'Jun 16, 2016 9:00:39 AM WARNING hudson.plugins.jira.JiraRestService getIssuejira rest client get issue error. cause: RestClientException{statusCode=Optional.of(404), errorCollections=[ErrorCollection{status=404, errors={}, errorMessages=[DER VORGANG EXISTIERT NICHT.]}]}Jun 16, 2016 9:00:39 AM WARNING hudson.plugins.jira.JiraChangeLogAnnotator annotateError getting remote issue PD-882099com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key PD-882099. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2383) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at hudson.plugins.jira.JiraSite.getIssue(JiraSite.java:424) at hudson.plugins.jira.JiraChangeLogAnnotator.annotate(JiraChangeLogAnnotator.java:101) at hudson.scm.ChangeLogSet$Entry.getMsgAnnotated(ChangeLogSet.java:252) at sun.reflect.GeneratedMethodAccessor242.invoke(Unknown Source) {noformat}
Add Comment
[JIRA] (JENKINS-36726) Plugin comments on subsequent successful builds
Title: Message Title Radek Antoniuk commented on JENKINS-36726 Re: Plugin comments on subsequent successful builds This is correct behavior. Currently repeated failures do not create a new issue but update the existing issue until the issue is closed. However it makes sense I guess to automatically resolve the issue when the build passes, is this what you mean? If yes, a PR implementing this in JiraCreateIssueNotifier will be more than welcome 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-36726) Plugin comments on subsequent successful builds
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-36726 Plugin comments on subsequent successful builds Change By: Radek Antoniuk Issue Type: Bug Improvement 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-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Robin Müller commented on JENKINS-36863 Re: [Gitlab plugin] Credentials drop-down doesn't show API token credential! Hi Tyrel Haveman, the plain-credentials plugin won't be installed automatically as this was marked as optional dependency with version 1.2.4. The plugin shouldn't require the plain-credentials anymore. The dependency is just there for backward compatibility. And an error within the backward compatibility code causes this bug. I fixed it by the following commit. So with the next release the plain-credentials plugin will be really an optional dependency. 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-33552) Settings validation fails on JiraRestService.getMyPermissions()
Title: Message Title Radek Antoniuk assigned an issue to Radek Antoniuk Jenkins / JENKINS-33552 Settings validation fails on JiraRestService.getMyPermissions() Change By: Radek Antoniuk Assignee: Radek Antoniuk 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-36726) Plugin comments on subsequent successful builds
Title: Message Title Radek Antoniuk assigned an issue to Radek Antoniuk Jenkins / JENKINS-36726 Plugin comments on subsequent successful builds Change By: Radek Antoniuk Assignee: Radek Antoniuk 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-35998) No issue update if at least one issue does not exists
Title: Message Title Radek Antoniuk assigned an issue to Radek Antoniuk Jenkins / JENKINS-35998 No issue update if at least one issue does not exists Change By: Radek Antoniuk Assignee: Radek Antoniuk 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-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Tyrel Haveman commented on JENKINS-36863 Re: [Gitlab plugin] Credentials drop-down doesn't show API token credential! I, the author of this Issue, have also found that adding the Plain Credentials Plugin solves my issue. Jenkins Developers: I don't know if there's a way for a plugin to require another plugin to be installed as a dependency, but if so, please add Plain Credentials Plugin as a dependency of the Gitlab plugin. I would consider that a resolution to this issue. If that is not possible, I would love to hear your alternative ideas. Thanks to joseph passavanti for figuring this out! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36977) JIRA plugin issue - jira plugin to validate my login/password and comments are not added to issues in jira
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-36977 JIRA plugin issue - jira plugin to validate my login/password and comments are not added to issues in jira Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37390) Add @Symbol("docker") to Docker Common's ToolDescriptor
Title: Message Title
Andrew Bayer updated JENKINS-37390
Jenkins / JENKINS-37390
Add @Symbol("docker") to Docker Common's ToolDescriptor
Change By:
Andrew Bayer
Status:
In Progress Review
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-37390) Add @Symbol("docker") to Docker Common's ToolDescriptor
Title: Message Title
Andrew Bayer commented on JENKINS-37390
Re: Add @Symbol("docker") to Docker Common's ToolDescriptor
PR up at https://github.com/jenkinsci/docker-commons-plugin/pull/52
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-37390) Add @Symbol("docker") to Docker Common's ToolDescriptor
Title: Message Title Andrew Bayer started work on JENKINS-37390 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37394) Add @Symbol("gradle") to Gradle's ToolDescriptor
Title: Message Title
Andrew Bayer updated JENKINS-37394
Jenkins / JENKINS-37394
Add @Symbol("gradle") to Gradle's ToolDescriptor
Change By:
Andrew Bayer
Status:
In Progress Review
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-37394) Add @Symbol("gradle") to Gradle's ToolDescriptor
Title: Message Title
Andrew Bayer commented on JENKINS-37394
Re: Add @Symbol("gradle") to Gradle's ToolDescriptor
PR up at https://github.com/jenkinsci/gradle-plugin/pull/35
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-33561) Coverity plugin does not use Perforce env variables when adding SCM data
Title: Message Title Chuck Aude commented on JENKINS-33561 Re: Coverity plugin does not use Perforce env variables when adding SCM data It appears that none of the standard P4 variables are used either, e.g. P4PORT, P4USER, P4CLIENT, P4TICKETS, P4TRUST, etc, implying that environment variables are not being read by this plugin. 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-37394) Add @Symbol("gradle") to Gradle's ToolDescriptor
Title: Message Title Andrew Bayer started work on JENKINS-37394 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37391) Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Title: Message Title
Andrew Bayer updated JENKINS-37391
Jenkins / JENKINS-37391
Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Change By:
Andrew Bayer
Status:
In Progress Review
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-37391) Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Title: Message Title
Andrew Bayer commented on JENKINS-37391
Re: Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
PR up - https://github.com/jenkinsci/git-client-plugin/pull/215
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-37391) Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Title: Message Title Andrew Bayer started work on JENKINS-37391 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37388) Add @Symbol("ant") to Ant's ToolDescriptor
Title: Message Title
Andrew Bayer updated JENKINS-37388
Jenkins / JENKINS-37388
Add @Symbol("ant") to Ant's ToolDescriptor
Change By:
Andrew Bayer
Status:
In Progress Review
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-37388) Add @Symbol("ant") to Ant's ToolDescriptor
Title: Message Title Andrew Bayer started work on JENKINS-37388 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37388) Add @Symbol("ant") to Ant's ToolDescriptor
Title: Message Title
Andrew Bayer commented on JENKINS-37388
Re: Add @Symbol("ant") to Ant's ToolDescriptor
PR up - https://github.com/jenkinsci/ant-plugin/pull/21
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-37386) Add @Symbol to ToolDescriptors
Title: Message Title Andrew Bayer commented on JENKINS-37386 Re: Add @Symbol to ToolDescriptors Just created tickets for a few plugins that need this done to start - I'll eventually try to work my way through all of the extensions of ToolInstallation. 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-37395) Add @Symbol("xvfb") to Xvfb's ToolDescriptor
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37395
Add @Symbol("xvfb") to Xvfb's ToolDescriptor
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
xvfb-plugin
Created:
2016/Aug/13 2:55 PM
Priority:
Minor
Reporter:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-37394) Add @Symbol("gradle") to Gradle's ToolDescriptor
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37394
Add @Symbol("gradle") to Gradle's ToolDescriptor
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
gradle-plugin
Created:
2016/Aug/13 2:54 PM
Priority:
Minor
Reporter:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-37392) Add @Symbol("msbuild") to MSBuild's ToolDescriptor
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37392
Add @Symbol("msbuild") to MSBuild's ToolDescriptor
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
msbuild-plugin
Created:
2016/Aug/13 2:53 PM
Priority:
Minor
Reporter:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-37393) Add @Symbol("mstestrunner") to MSTestRunner's ToolDescriptor
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37393
Add @Symbol("mstestrunner") to MSTestRunner's ToolDescriptor
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
mstestrunner-plugin
Created:
2016/Aug/13 2:53 PM
Priority:
Minor
Reporter:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed
[JIRA] (JENKINS-37391) Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37391
Add @Symbol("git") (and "jgit") to Git Client's ToolDescriptors
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
git-client-plugin
Created:
2016/Aug/13 2:49 PM
Priority:
Minor
Reporter:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed
[JIRA] (JENKINS-37390) Add @Symbol("docker") to Docker Common's ToolDescriptor
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37390
Add @Symbol("docker") to Docker Common's ToolDescriptor
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
docker-commons-plugin
Created:
2016/Aug/13 2:47 PM
Priority:
Minor
Reporter:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-37389) Add @Symbol("custom") to Custom Tool's ToolDescriptor
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37389
Add @Symbol("custom") to Custom Tool's ToolDescriptor
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
customtools-plugin
Created:
2016/Aug/13 2:46 PM
Priority:
Minor
Reporter:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-37387) Add @Symbol("ansible") to Ansible's ToolDescriptor
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37387
Add @Symbol("ansible") to Ansible's ToolDescriptor
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
ansible-plugin
Created:
2016/Aug/13 2:44 PM
Priority:
Minor
Reporter:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-37388) Add @Symbol("ant") to Ant's ToolDescriptor
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37388
Add @Symbol("ant") to Ant's ToolDescriptor
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
ant-plugin
Created:
2016/Aug/13 2:44 PM
Priority:
Minor
Reporter:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-37386) Add @Symbol to ToolDescriptors
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37386 Add @Symbol to ToolDescriptors Issue Type: Epic Assignee: Andrew Bayer Components: core Created: 2016/Aug/13 2:42 PM Priority: Minor Reporter: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-31875) No working folder mapping when accessing TFS (win 10)
Title: Message Title Ray Hallquist commented on JENKINS-31875 Re: No working folder mapping when accessing TFS (win 10) Turning Use Update resolved the issue for me. I have spaces in the Workspace path. 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-31875) No working folder mapping when accessing TFS (win 10)
Title: Message Title Ray Hallquist edited a comment on JENKINS-31875 Re: No working folder mapping when accessing TFS (win 10) Turning Use Update off resolved the issue for me.I have spaces in the Workspace path. 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-36080) docker 1.12 breaks plugin because of HostConfig
Title: Message Title
Phillip Wirth edited a comment on JENKINS-36080
Re: docker 1.12 breaks plugin because of HostConfig
I made a Pull Request https://github.com/jenkinsci/docker-plugin/pull/418 well it dosen't build, since the branch I used, your {{docker-java-nex}} has this SNAPSHOT dependency .. My Testing environment:Debian jessie with docker 1.12.0Fedora with docker version 1.12.0Jenkins was running in docker as well from the image jenkins.
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-36080) docker 1.12 breaks plugin because of HostConfig
Title: Message Title Phillip Wirth commented on JENKINS-36080 Re: docker 1.12 breaks plugin because of HostConfig I made a Pull Request https://github.com/jenkinsci/docker-plugin/pull/418 well it dosen't build, since the branch I used, your docker-java-nex has this SNAPSHOT dependency .. 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-37350) Don't use random for Filename in Save to Workspace option
Title: Message Title David van Laatum closed an issue as Fixed merged Jenkins / JENKINS-37350 Don't use random for Filename in Save to Workspace option Change By: David van Laatum Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Robin COLLAS commented on JENKINS-36863 Re: [Gitlab plugin] Credentials drop-down doesn't show API token credential! I have installed Plain Credentiles Plugin and now it's work. Thank you for your help joseph passavanti ! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37196) DSL for Violation Comments to GitHub Plugin
Title: Message Title Tomas Bjerre closed an issue as Fixed Jenkins / JENKINS-37196 DSL for Violation Comments to GitHub Plugin Change By: Tomas Bjerre Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
