[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-59192 configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Change By: Dominik Bartholdi Component/s: config-file-provider-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.16531.1587646800614%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-59192 configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Change By: Dominik Bartholdi Component/s: config-file-provider-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.16527.1587646800415%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title Dominik Bartholdi commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) James Green that sounds like the exact same case then Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.3725.1579691340259%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title Dominik Bartholdi commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) Raihaan Shouhell sure, I do my best to get you the required details: All I do is done with cloudformation, so it should be reproducible. Everytime we install a new version, i create it from scratch: I remove everything and build it up from ground with cloudformation only (no manual steps and no cloudformation updates). You can find a stripped down version of the cloudformation templates here: https://gist.github.com/imod/fb702d545dbe77292e8f4796c7804059 The templates should contain all the details you need. The 'vpc-cloudformation-template,json' creates the full VPC with route tables, subnet and gateway and can be executed as is, but I had to remove quite a bit from the 'jenkins-cloudformation-template,json' - this one would install Jenkins on a EC2 instance and configure the security groups. I hope this is useful, if you don't get a long with cloudformation, please let me know. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.3645.1579680900314%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title Dominik Bartholdi commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) Raihaan Shouhell I had the exact same issue - lucky me, I was able to compare two EC2 instances (one launched with the old EC2-plugin version and one with the new one). The only difference I found was the assignement of a public IP. As soon as I assigned a public IP to the instance launched by the new version, it all worked again. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.3113.1579595400278%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-60407 Launched instances cannot reach public internet (regression) Change By: Dominik Bartholdi Attachment: image-2020-01-17-09-31-03-387.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.905.1579249920455%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title Dominik Bartholdi commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) JCasC is an additional plugin to treat jenkins configuration as code: https://plugins.jenkins.io/configuration-as-code But you will find the option in the UI too: http://myjenkins/configure > cloud > Amazon EC2 > AMIs > Advanced > 'Associate Public IP' Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.908.1579249920528%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-60407
Re: Launched instances cannot reach public internet (regression)
I was able to fix the issue by adding this to the JasC Config of the ec2 plugin: {code:java} associatePublicIp: true { { code } }
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.6548.1578673920280%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title
Dominik Bartholdi commented on JENKINS-60407
Re: Launched instances cannot reach public internet (regression)
I was able to fix the issue by adding this to the JasC Config of the ec2 plugin: associatePublicIp: true {{}}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.6545.1578673860283%40Atlassian.JIRA.
[JIRA] (JENKINS-60407) Launched instances cannot reach public internet (regression)
Title: Message Title Dominik Bartholdi commented on JENKINS-60407 Re: Launched instances cannot reach public internet (regression) we have the exact same issue, I think this is caused by JENKINS-58578 I did some manual testing and setting a public IP on the agent solves the issue - this IP is set automatically on an agent launched with ec2-plugin:1.45 -> we had to go back to 1.45 too Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203464.1575911038000.6508.1578668220220%40Atlassian.JIRA.
[JIRA] (JENKINS-60695) "Filter by AWS secret namespace ID" not working
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-60695
"Filter by AWS secret namespace ID" not working
Issue Type:
Bug
Assignee:
Chris Kilding
Components:
aws-secrets-manager-credentials-provider-plugin
Created:
2020-01-08 13:40
Priority:
Major
Reporter:
Dominik Bartholdi
I created credentials like this:
aws secretsmanager create-secret --name 'jks/DB_USER_X' --secret-string 'zz' --tags 'Key=jenkins:credentials:username,Value=u' --description ''
Then I used the documented policy template: https://github.com/jenkinsci/aws-secrets-manager-credentials-provider-plugin/blob/master/docs/iam/secret-namespace-id.json to filter credentials by a namespace. My complete policy looked like this:
{
"Version": "2012-10-17",
"Statement": [
{
"Action": "secretsmanager:GetSecretValue",
"Resource": "arn:aws:secretsmanager:::secret:jks/*",
"Effect": "Allow"
},
{
"Action": "secretsmanager:ListSecrets",
"Resource": "*",
"Effect": "Allow"
}
]
}
unfortunate this ends up in this error:
com.cloudbees.plugins.credentials.CredentialsUnavailableException:
[JIRA] (JENKINS-60692) credential type icon not correctly reflected
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-60692 credential type icon not correctly reflected Issue Type: Bug Assignee: Chris Kilding Attachments: Screenshot 2020-01-08 at 10.00.12.png Components: aws-secrets-manager-credentials-provider-plugin Created: 2020-01-08 13:25 Priority: Minor Reporter: Dominik Bartholdi I created a username/password credentials with the following command: aws secretsmanager create-secret --name 'DB_USER_X' --secret-string 'zz' --tags 'Key=jenkins:credentials:username,Value=u' --description '' although this worked and the credentials also show up in jenkins, the credentials have the wrong type icon shown in the credentials list screen: all four credentials shown in the above screenshot should have the same icon in the first position of each line - all should be of type "UserName with Password". Currently the ones from AWS Provider show a different icon with the tool tip "AWS Secrets Manager secret" (which in fact is the icon for "Secret text"). This is very irritating for a user.
[JIRA] (JENKINS-60652) plugin breaks jenkins without a connection to AWS
Title: Message Title Dominik Bartholdi commented on JENKINS-60652 Re: plugin breaks jenkins without a connection to AWS maybe its worth breaking this issue up into multiple, meaning: fix the low hanging fruits. After all, I think a plugin should never make jenkins unusable just because it is installed but not configured and not used. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203894.157833410.3633.1578400260248%40Atlassian.JIRA.
[JIRA] (JENKINS-60652) plugin breaks jenkins without a connection to AWS
Title: Message Title Dominik Bartholdi commented on JENKINS-60652 Re: plugin breaks jenkins without a connection to AWS Thanks for the info - I have my setup similar to yours (with CloudFormation, JasC), but until now, the Jenkins Docker Image I create also used to work on my local env (my mac) - but now this unfortunately is not the case anymore and its harder to do some first local testing of the image. The most important part for me right now is your first part "Listing credentials" - this effectively hinders my workflow right now. I don't know the internals of the credential providers, but from a users point of view: I have a job configured e.g. a pipeline and the only thing to reference credentials are by a string-id. For me as a pipeline admin, I don't care which provider actually holds the credentials. If it is not found by any of the providers, it should throw an exception. So there is no way for me to say that I want this credentials retrieved rather from AWS and not from the internal jenkins provider. Saying this, I don't understand why a provider should throw an exception if it can't resolve credentials for a given ID (unless the credentials framework swallows the exceptions and interprets it as a "NotFound" to hand over to the next provider installed until one can resolve it). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60652) plugin breaks jenkins without a connection to AWS
Title: Message Title
Dominik Bartholdi updated an issue
Jenkins / JENKINS-60652
plugin breaks jenkins without a connection to AWS
Change By:
Dominik Bartholdi
when ever this plugin does not have a connection to AWS it breaks many screens. e.g. every screen which wants to list some credentials in a dropdown will show an error message e.g. in [http://localhost:8080/configure] when the [docker-commons-plugin|https://plugins.jenkins.io/docker-commons] or [cloudbees-bitbucket-branch-source-plugin|https://plugins.jenkins.io/cloudbees-bitbucket-branch-source] is installed. Also all build accessing any credential will fail, even if the credentials requested by the build are provided by a different credentials-provider (e.g. default jenkins provider).This can easily reproduced by just installing the plugin on a local instance and not configuring anything more. The exception looks like this:{code:java}com.amazonaws.SdkClientException: Unable to find a region via the region provider chain. Must provide an explicit region in the builder or setup environment to supply a region. at com.amazonaws.client.builder.AwsClientBuilder.setRegion(AwsClientBuilder.java:462) at com.amazonaws.client.builder.AwsClientBuilder.configureMutableProperties(AwsClientBuilder.java:424) at com.amazonaws.client.builder.AwsSyncClientBuilder.build(AwsSyncClientBuilder.java:46) at io.jenkins.plugins.credentials.secretsmanager.AwsCredentialsProvider.fetchCredentials(AwsCredentialsProvider.java:103) at com.google.common.base.Suppliers$ExpiringMemoizingSupplier.get(Suppliers.java:173) at io.jenkins.plugins.credentials.secretsmanager.AwsCredentialsProvider.getCredentials(AwsCredentialsProvider.java:61) at com.cloudbees.plugins.credentials.CredentialsProvider.getCredentials(CredentialsProvider.java:1147) at com.cloudbees.plugins.credentials.CredentialsProvider.getCredentials(CredentialsProvider.java:1222) at com.cloudbees.plugins.credentials.CredentialsProvider.lookupCredentials(CredentialsProvider.java:549) at com.cloudbees.plugins.credentials.CredentialsProvider.findCredentialById(CredentialsProvider.java:906) at com.cloudbees.plugins.credentials.CredentialsProvider.findCredentialById(CredentialsProvider.java:850) at org.jenkinsci.plugins.credentialsbinding.MultiBinding.getCredentials(MultiBinding.java:144) at org.jenkinsci.plugins.credentialsbinding.impl.UsernamePasswordMultiBinding.bind(UsernamePasswordMultiBinding.java:75) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2.doStart(BindingStep.java:135) {code}
[JIRA] (JENKINS-60652) plugin breaks jenkins without a connection to AWS
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-60652 plugin breaks jenkins without a connection to AWS Change By: Dominik Bartholdi Summary: plugin breaks most jenkins functionality without a connection to AWS Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203894.157833410.2921.1578334205051%40Atlassian.JIRA.
[JIRA] (JENKINS-60652) plugin breaks most jenkins functionality without a connection to AWS
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-60652 plugin breaks most jenkins functionality without a connection to AWS Issue Type: Bug Assignee: Chris Kilding Components: aws-secrets-manager-credentials-provider-plugin Created: 2020-01-06 18:08 Environment: Jenkins: 2.204.1 aws-secrets-manager-credentials-provider: 0.1.2 Priority: Major Reporter: Dominik Bartholdi when ever this plugin does not have a connection to AWS it breaks many screens. e.g. every screen which wants to list some credentials in a dropdown will show an error message e.g. in http://localhost:8080/configure when the docker-commons-plugin or cloudbees-bitbucket-branch-source-plugin is installed. Also all build accessing any credential will fail, even if the credentials requested by the build are provided by a different credentials-provider (e.g. default jenkins provider). This can easily reproduced by just installing the plugin on a local instance and not configuring anything more. Add Comment
[JIRA] (JENKINS-60605) GIT_ASKPASS not working anymore
Title: Message Title Dominik Bartholdi closed an issue as Not A Defect this issue was related to a change in the ec2 plugin and has nothing to do with the git plugin Jenkins / JENKINS-60605 GIT_ASKPASS not working anymore Change By: Dominik Bartholdi Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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-60605) GIT_ASKPASS not working anymore
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-60605 GIT_ASKPASS not working anymore Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-12-30 09:10 Environment: jenkins:2.204.1 git:4.0.0 git-client:3.0.0 git-server:1.9 Priority: Critical Reporter: Dominik Bartholdi I have a multi branch project setup, within the pipeline I do an additional fetch with the help of 'GIT_ASKPASS' as I described here: https://github.com/imod/jenkins-git-askpass-pipeline-lib with this plugin combination it is working: jenkins:2.176.2 git:3.12.0 git-client:2.8.1 git-server:1.8 with this plugin combination it is NOT working anymore: jenkins:2.204.1 git:4.0.0 git-client:3.0.0 git-server:1.9 the error I get is this: Cloning repository https://bitbucket.org//dummy.git > git init /home/ec2-user/workspace/org_dummy_develop # timeout=10 Fetching upstream changes from https://bitbucket.org//dummy.git > git --version # timeout=10 using GIT_ASKPASS to set credentials YOOBOT_BITBUCKET > git fetch --no-tags --progress -- https://bitbucket.org//dummy.git +refs/heads/develop:refs/remotes/origin/develop # timeout=10 ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command
[JIRA] (JENKINS-59841) Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts)
Title: Message Title Dominik Bartholdi commented on JENKINS-59841 Re: Scriptler 3.1 destroys groovy scripts containing German special characters (Umlauts) Robert Nitschke could you please check wether the files are also saved with the wrong encoding on the disc? at /scriptler/scripts?*.groovy and could you attach a simple example file? thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202576.1571392265000.10316.1571396400427%40Atlassian.JIRA.
[JIRA] (JENKINS-30267) Maven repository artifact does not showing newly updated version from Nexus Maven Repository
Title: Message Title Dominik Bartholdi assigned an issue to Unassigned Jenkins / JENKINS-30267 Maven repository artifact does not showing newly updated version from Nexus Maven Repository Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164854.1441201253000.856.1570170240869%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Dominik Bartholdi assigned an issue to Carlos Sanchez Jenkins / JENKINS-59192 configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.5330.1567495740197%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Dominik Bartholdi commented on JENKINS-59192 Re: configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines As the config-file-provider did not change, this seems more an issue caused on the kubernetes site. As I never worked with kubernetes, this will definitely need to be fixed by someone who does know how k8 works. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.5326.1567495680223%40Atlassian.JIRA.
[JIRA] (JENKINS-58668) Doesn't create a file within docker.inside {}
Title: Message Title
Dominik Bartholdi resolved as Not A Defect
Chad Gilbert many thanks for the detailed explanation! I fully agree and therefore will resolve this issue
Jenkins / JENKINS-58668
Doesn't create a file within docker.inside {}
Change By:
Dominik Bartholdi
Status:
Open Resolved
Resolution:
Not A Defect
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200950.1564129139000.6663.1566367320534%40Atlassian.JIRA.
[JIRA] (JENKINS-58668) Doesn't create a file within docker.inside {}
Title: Message Title
Dominik Bartholdi commented on JENKINS-58668
Re: Doesn't create a file within docker.inside {}
hmm, good catch - need to investigate to see how this is even doable...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200950.1564129139000.6049.1564727880211%40Atlassian.JIRA.
[JIRA] (JENKINS-58040) listing of available archetypes not working
Title: Message Title Dominik Bartholdi commented on JENKINS-58040 Re: listing of available archetypes not working placed a PR: https://github.com/jenkinsci/archetypes/pull/42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200060.1560760521000.2416.1560861000349%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58063) Config File Provider plugin 3.6.1 not available
Title: Message Title Dominik Bartholdi resolved as Fixed don't really know what the issue was, but I just released 3.6.2: http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/config-file-provider/3.6.2/ Jenkins / JENKINS-58063 Config File Provider plugin 3.6.1 not available Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200085.1560842698000.2400.1560859860297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58040) listing of available archetypes not working
Title: Message Title Dominik Bartholdi commented on JENKINS-58040 Re: listing of available archetypes not working thanks Jesse Glick! apparently defining a mirror like this will make the archetype not to resolve the archetypes anymore: repo.jenkins-ci.org-all http://repo.jenkins-ci.org/public * not sure, but it might be related to the repository index information which can't be retrieved anymore (or not complete) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200060.1560760521000.1769.1560778800104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58040) listing of available archetypes not wokring
Title: Message Title Dominik Bartholdi assigned an issue to Jesse Glick Jenkins / JENKINS-58040 listing of available archetypes not wokring Change By: Dominik Bartholdi Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200060.1560760521000.1553.1560761700110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58040) listing of available archetypes not wokring
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-58040 listing of available archetypes not wokring Issue Type: Bug Assignee: Unassigned Components: archetypes Created: 2019-06-17 08:35 Environment: platypus:tmp domi$ mvn -version Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00) Maven home: /Users/domi/.sdkman/candidates/maven/current Java version: 1.8.0_121, vendor: Oracle Corporation, runtime: /Users/domi/.sdkman/candidates/java/8u121/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.14.5", arch: "x86_64", family: "mac" Priority: Minor Reporter: Dominik Bartholdi The documentation at https://github.com/jenkinsci/archetypes explains the following command to list all currently released jenkins archetypes: platypus:tmp domi$ mvn archetype:generate -Dfilter=io.jenkins.archetypes: [INFO] Scanning for projects... [INFO] [INFO] --< org.apache.maven:standalone-pom >--- [INFO] Building Maven Stub Project (No POM) 1 [INFO] [ pom ]- [INFO] [INFO] >>> maven-archetype-plugin:3.1.0:generate (default-cli) > generate-sources @ standalone-pom >>> [INFO] [INFO] <<< maven-archetype-plugin:3.1.0:generate (default-cli) < generate-sources @ standalone-pom <<< [INFO] [INFO] [INFO] --- maven-archetype-plugin:3.1.0:generate (default-cli) @ standalone-pom --- [INFO] Generating project in Interactive mode [INFO] Your filter doesn't match any archetype, so try again with another value. [INFO]
[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin
Title: Message Title Dominik Bartholdi commented on JENKINS-56305 Re: Need some help with init scripts on this plugin ios is the name of the folder Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197885.155124611.570.1560495300243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin
Title: Message Title
Dominik Bartholdi commented on JENKINS-56305
Re: Need some help with init scripts on this plugin
as described above, you should not do it this way and I can't guarantee this will always work! But for sure this words will not stop you from doing so, therefore I show you at least a better way to do it: (Please never interact with the *Provider classes at all):
def folder = Jenkins.instance.getItemByFullName('ios');
def action = ""
def store = action.getStore();
def config = new org.jenkinsci.plugins.configfiles.json.JsonConfig("_config", "Config for ", "Branch config ", "{A:B}");
// save the new config
store.save(config);
// get the new config
def jsonConfig = store.getById("_config");
// remove the config
store.remove("_config");
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197885.155124611.25722.1560317700310%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48430) Provided config file is sometimes not complete
Title: Message Title Dominik Bartholdi commented on JENKINS-48430 Re: Provided config file is sometimes not complete I would very much like to fix this, but as stated previously, I'm not able to reproduce the issue in my env. I have an idea for a fix, but would need someone to try it before I ship it. Anyone willing to help/test out? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187028.1512645914000.25261.1560266880250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57417) configFileProvider / withCredentials not working in declarative pipeline
Title: Message Title Dominik Bartholdi updated JENKINS-57417 released with 3.6.1 Jenkins / JENKINS-57417 configFileProvider / withCredentials not working in declarative pipeline Change By: Dominik Bartholdi Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199223.1557587492000.21674.1559719981138%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56922) FolderConfigFileAction.doShow NullPointerException
Title: Message Title
Dominik Bartholdi commented on JENKINS-56922
Re: FolderConfigFileAction.doShow NullPointerException
I can reproduce an issue at the same action, but it appears with a different error. I get:
404 Not Found
Stapler processed this HTTP request as follows, but couldn't find the resource to consume the request
-> evaluate( :hudson.model.Hudson,"/job/JENKINS-48430/configfiles/show")
-> evaluate(((StaplerProxy)).getTarget(),"/job/JENKINS-48430/configfiles/show")
-> evaluate(.getJob("JENKINS-48430"),"/configfiles/show")
-> evaluate( :org.jenkinsci.plugins.workflow.job.WorkflowJob,"/configfiles/show")
-> evaluate(.getDynamic("configfiles",...),"/show")
org.jenkinsci.plugins.workflow.job.WorkflowJob@c964a9e[JENKINS-48430].getDynamic("configfiles",...)==null. Back tracking.
-> No matching rule was found on for "/configfiles/show"
has the following URL mappings, in the order of preference:
1. If path ends without '/' insert it
2. delete() for url=/ with DELETE
3. hudson.model.Job.doRssChangelog(...) for url=""
4. org.jenkinsci.plugins.workflow.job.WorkflowJob.doCancelQueue(...) for url=""
5. hudson.model.Job.doDoRename(...) for url=""
...
how can I reproduce the same error as you see it?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198599.155456968.21671.1559719860320%40Atlassian.JIRA.
For more options, visit
[JIRA] (JENKINS-56922) FolderConfigFileAction.doShow NullPointerException
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-56922 Re: FolderConfigFileAction.doShow NullPointerException - please provide some more information... - * - what do you try to do? - * - what configuration file type are you working with? - * - does the config file still exist or has it been deleted? - * - maybe screenshots - * - ... -sorry, i got it now... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198599.155456968.21666.1559718480254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44022) Environment variable not replaced in config file
Title: Message Title Dominik Bartholdi resolved as Fixed Jenkins / JENKINS-44022 Environment variable not replaced in config file Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181560.1493820406000.21651.1559717340440%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48562) Inline Environment Variables not replaced in config file
Title: Message Title Dominik Bartholdi resolved as Fixed resolved with 3.6.1 Jenkins / JENKINS-48562 Inline Environment Variables not replaced in config file Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187182.1513258885000.21647.1559717280355%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54416) Configure Systems Page Showing Oops Page. Unable to Save
Title: Message Title Dominik Bartholdi resolved as Fixed Jenkins / JENKINS-54416 Configure Systems Page Showing Oops Page. Unable to Save Change By: Dominik Bartholdi Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195174.154113240.21644.1559717160183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56828) 更新系统配置的相关参数时，保存不了，jenkins报错。
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-56828 更新系统配置的相关参数时，保存不了，jenkins报错。 Change By: Dominik Bartholdi Component/s: hello-world-plugin Component/s: config-file-provider-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198485.1554105956000.21642.1559717100238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56922) FolderConfigFileAction.doShow NullPointerException
Title: Message Title Dominik Bartholdi commented on JENKINS-56922 Re: FolderConfigFileAction.doShow NullPointerException please provide some more information... what do you try to do? what configuration file type are you working with? does the config file still exist or has it been deleted? maybe screenshots ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198599.155456968.21639.1559717040190%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57646) Pipeline "when" condition is evaluated on the node
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-57646 Pipeline "when" condition is evaluated on the node Change By: Dominik Bartholdi Component/s: declarative-pipeline-when-conditions-plugin Component/s: conditional-buildstep-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199577.1558621197000.10852.1558677780374%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57646) Pipeline "when" condition is evaluated on the node
Title: Message Title Dominik Bartholdi assigned an issue to Andrew Bayer Jenkins / JENKINS-57646 Pipeline "when" condition is evaluated on the node Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199577.1558621197000.10857.1558677780446%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46579) Maven Event Spy seems to still have a thread safe problem
Title: Message Title Dominik Bartholdi reopened an issue we run version 3.6.11 and still see this from time to time: ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /home/ec2-user/workspace/org_yooture_develop@tmp/withMaven5705f0d0/maven-spy-20190520-135648-9715492809875305253764.log, ignore file. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 18407; columnNumber: 263; XML document structures must start and end within the same entity. Jenkins / JENKINS-46579 Maven Event Spy seems to still have a thread safe problem Change By: Dominik Bartholdi Resolution: Fixed Status: Closed Reopened Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment
[JIRA] (JENKINS-57417) configFileProvider / withCredentials not working in declarative pipeline
Title: Message Title
Dominik Bartholdi edited a comment on JENKINS-57417
Re: configFileProvider / withCredentials not working in declarative pipeline
Why do you handle the ids different for {{withCredentials}} and {{configFileProvider}}? {{fileId}} is not substituted by the configFileProvider, therefore you have to pass the id as it is. But after all you can use groovy if you like, this should work:{code:java}var pipFile = '05f48227-0980-4313-ab24-f007d78090cf'pipeline {agent any environment {PIP_FILE = '05f48227-0980-4313-ab24-f007d78090cf'} stages {stage('Build') {steps {withCredentials([usernamePassword(credentialsId: '0353637f-ef0b-46e5-b95a-6322b1e073d7', passwordVariable: 'PIP_PASSWORD', usernameVariable: 'PIP_USERNAME')]) {configFileProvider([configFile(fileId: pipFile, replaceTokens: true, variable: 'PIP_TARGET')]) { sh "cat ${PIP_TARGET}"}}}}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199223.1557587492000.1655.1557761760351%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57417) configFileProvider / withCredentials not working in declarative pipeline
Title: Message Title Dominik Bartholdi resolved as Not A Defect Jenkins / JENKINS-57417 configFileProvider / withCredentials not working in declarative pipeline Change By: Dominik Bartholdi Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199223.1557587492000.1652.1557761760315%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57417) configFileProvider / withCredentials not working in declarative pipeline
Title: Message Title
Dominik Bartholdi commented on JENKINS-57417
Re: configFileProvider / withCredentials not working in declarative pipeline
Why do you handle the ids different for withCredentials and configFileProvider? fileId is not substituted by the configFileProvider, therefore you have to pass the id as it is. But after all you can use groovy if you like, this should work:
var pipFile = '05f48227-0980-4313-ab24-f007d78090cf'
pipeline {
agent any
environment {
PIP_FILE = '05f48227-0980-4313-ab24-f007d78090cf'
}
stages {
stage('Build') {
steps {
withCredentials([usernamePassword(credentialsId: '0353637f-ef0b-46e5-b95a-6322b1e073d7', passwordVariable: 'PIP_PASSWORD', usernameVariable: 'PIP_USERNAME')]) {
configFileProvider([configFile(fileId: pipFile, replaceTokens: true, variable: 'PIP_TARGET')]) {
sh "cat ${PIP_TARGET}"
}
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199223.1557587492000.1649.1557761700126%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Dominik Bartholdi commented on JENKINS-57324 Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch Cyrille Le Clerc do you have any idea what could be causing this? If this is really caused by the config-file-provider, then I would suspect it here https://github.com/jenkinsci/config-file-provider-plugin/blob/master/src/main/java/org/jenkinsci/lib/configprovider/model/ConfigFileManager.java#L95-L101 - but to be hownest I have no idea why this should be the case and I have no way to test on windows... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.1645.1557760500204%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title
Dominik Bartholdi commented on JENKINS-57324
Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch
can you please explain what are the values of ${env.MAVEN_VERBOSE} and ${env.RELEASE_VERSION_PARAMETERS}?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54861) don't trigger initial build after branch detection
Title: Message Title Dominik Bartholdi resolved as Duplicate https://www.cloudbees.com/blog/skipping-first-build-first-branch-indexing Jenkins / JENKINS-54861 don't trigger initial build after branch detection Change By: Dominik Bartholdi Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56922) FolderConfigFileAction.doShow NullPointerException
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-56922 FolderConfigFileAction.doShow NullPointerException Change By: Dominik Bartholdi Priority: Major Trivial Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56828) 更新系统配置的相关参数时，保存不了，jenkins报错。
Title: Message Title Dominik Bartholdi commented on JENKINS-56828 Re: 更新系统配置的相关参数时，保存不了，jenkins报错。 sorry, unfortunate I don't understand what you have written in the issue description... but the stacktrace does not seem related to the config-file-provider-plugin - but to some sort of a HelloWorld example Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56516) Variable substitution issue when using configuration as code to create managed config files
Title: Message Title Dominik Bartholdi resolved as Not A Defect Jenkins / JENKINS-56516 Variable substitution issue when using configuration as code to create managed config files Change By: Dominik Bartholdi Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56516) Variable substitution issue when using configuration as code to create managed config files
Title: Message Title Dominik Bartholdi updated JENKINS-56516 Jenkins / JENKINS-56516 Variable substitution issue when using configuration as code to create managed config files Change By: Dominik Bartholdi Resolution: Not A Defect Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56305) Need some help with init scripts on this plugin
Title: Message Title Dominik Bartholdi resolved as Not A Defect not sure this works, but your probably better off to use `org.jenkinsci.plugins.configfiles.GlobalConfigFiles.save(config)` then any of the providers directly. But that sad, you should better use a plugin designed to do this: JobDSL Plugin: https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-DSL-Commands#config-file Configuration as Code Plugin: https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/config-file-provider Jenkins / JENKINS-56305 Need some help with init scripts on this plugin Change By: Dominik Bartholdi Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56275) Conditional Action doesn't treat Parameterized Timer Trigger as Timer Trigger
Title: Message Title Dominik Bartholdi commented on JENKINS-56275 Re: Conditional Action doesn't treat Parameterized Timer Trigger as Timer Trigger sorry, I have no idea what this is all about, please provide some more background... what plugins are involved? how to reproduce? ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56237) IllegalArgumentException: providerId can NOT be null when using npmConfig
Title: Message Title Dominik Bartholdi assigned an issue to Nikolas Falco Jenkins / JENKINS-56237 IllegalArgumentException: providerId can NOT be null when using npmConfig Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56237) IllegalArgumentException: providerId can NOT be null when using npmConfig
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-56237 IllegalArgumentException: providerId can NOT be null when using npmConfig Change By: Dominik Bartholdi Component/s: nodejs-plugin Component/s: config-file-provider-plugin Component/s: job-dsl-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50718) append tool HOME to PATH in declarative Pipeline
Title: Message Title Dominik Bartholdi commented on JENKINS-50718 Re: append tool HOME to PATH in declarative Pipeline Oleg Nenashev no, its not related to Jenkins X - it just happens that we use a Tool provided by Jenkins X in a standalone way Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50718) append tool HOME to PATH in declarative Pipeline
Title: Message Title Dominik Bartholdi commented on JENKINS-50718 Re: append tool HOME to PATH in declarative Pipeline Oleg Nenashev no, its not related to Jenkins X - it just happens that we use a Tool provided by Jenkins X in a standalone way Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50718) append tool HOME to PATH in declarative Pipeline
Title: Message Title Dominik Bartholdi commented on JENKINS-50718 Re: append tool HOME to PATH in declarative Pipeline Oleg Nenashev no, its not related to Jenkins X - it just happens that we use a Tool provided by Jenkins X in a standalone way Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Dominik Bartholdi commented on JENKINS-55013 Re: support for App Center As hockeyapp has a clear enddate (November 2019) maybe its better to just start from scratch - this way you don't have to deal with legacy and users are clear about it too. Thats at least what I would do in this case... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-55013 support for App Center Change By: Dominik Bartholdi On November 16, 2019, HockeyApp will transition fully to App Centerwill this plugin also support App Center? see [https://hockeyapp.net|https://hockeyapp.net/] for more info Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55013) support for App Center
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-55013 support for App Center Issue Type: Story Assignee: Mez Pahlan Components: hockeyapp-plugin Created: 2018-12-04 15:18 Priority: Minor Reporter: Dominik Bartholdi On November 16, 2019, HockeyApp will transition fully to App Center will this plugin also support App Center? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54996) automatically setup of triggers on main repo
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-54996
automatically setup of triggers on main repo
Issue Type:
New Feature
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-12-04 07:30
Priority:
Major
Reporter:
Dominik Bartholdi
currently webhooks (e.g. github or bitbucket) are only active after the first run of the pipeline. e.g. the following pipeline will not be triggered by a bitbucket commit hook until the build was kicked of manually at least once:
pipelineJob("install") {
triggers {
bitbucketPush()
}
definition {
cpsScm {
scm {
git {
remote {
url('https://bitbucket.org/myorg/myrepo')
credentials('BITBUCKET_CRED')
}
branches('develop')
scriptPath(’install.groovy')
lightweight(true)
extensions {
localBranch()
cleanCheckout()
}
}
}
}
}
}
This issue requests to automatically setup triggers for the main repo at job creation/ modification. This would ease the setup of such jobs with the job-dsl plugin a lot. No further manual triggering would be required.
[JIRA] (JENKINS-54908) allow delay of starting new instances
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54908 allow delay of starting new instances Issue Type: New Feature Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2018-11-28 09:03 Priority: Minor Reporter: Dominik Bartholdi I would like to have an option to configure the ec2 plugin to wait before it starts a new ec2 instance. e.g. If I have an ec2 agent running, then I would like jenkins to wait for X-minutes before it starts an other instance. During this time the already running agent might get available and then there is no need to start a second instance. btw. I'm not sure what I missed, but I'm not able to see the value for instanceCapStr anywhere on the UI... Add Comment
[JIRA] (JENKINS-54878) remove items not managed by job-dsl
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-54878
remove items not managed by job-dsl
Issue Type:
New Feature
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-11-27 10:33
Priority:
Minor
Reporter:
Dominik Bartholdi
I was hoping that
jobDsl targets: ['jobs/*.groovy', 'config-files/*.groovy', 'views/*.groovy'].join('\n'),
removedJobAction: 'DELETE',
removedViewAction: 'DELETE',
removedConfigFilesAction: 'DELETE',
lookupStrategy: 'JENKINS_ROOT',
unstableOnDeprecation: true,
failOnMissingPlugin: true
would also delete all jobs not managed by job-dsl - unfortunate its not. If job-dsl would have an option to remove everything it does not know about (jobs, configFiles, views) then keeping the environment cleaner would be a lot easier. Our organization could define a rule saying: 'all our items must be created via job-dsl and be reproducible everything else will be deleted. Therefore I ask for a feature to enforce job-dsl to only keep items it knows about.
[JIRA] (JENKINS-54877) missing elements in job dsl 'organizationFolder'
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-54877
missing elements in job dsl 'organizationFolder'
Issue Type:
Improvement
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-11-27 10:14
Environment:
Jenkins:2.138.2 job-dsl:1.70 cloudbees-bitbucket-branch-source:2.2.15 basic-branch-build-strategies:1.1.1
Priority:
Minor
Reporter:
Dominik Bartholdi
While configuring our bitbucket organization folder, I came across a couple of places where I needed to use the configure block because it did not work the way I expected:
'organizationFolder' / 'triggers' / 'periodic' not working as expected, no matter what value I use, it always falls back to 1 minute
'organizationFolder' / 'traits' does not support BranchDiscoveryTrait
'organizationFolder' does not support 'buildStrategies'
organizationFolder('org') {
description('This contains branch source jobs for Bitbucket')
displayName('org')
// triggers {
// // not working, using configure block below
// periodic(2880)
// }
organizations {
bitbucket {
repoOwner('myorg')
credentialsId('BITBUCKET_CRED')
traits {
// BranchDiscoveryTrait not available using configure block below
}
}
}
//
[JIRA] (JENKINS-54467) Evergreen AWS flavor security hardening
Title: Message Title Dominik Bartholdi commented on JENKINS-54467 Re: Evergreen AWS flavor security hardening I think JENKINS-54633 - install evergreen in a dedicated VPC, is a first step into this direction Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Dominik Bartholdi assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-54872 Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title
Dominik Bartholdi commented on JENKINS-54872
Re: Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
the feature you request is not provided by the config-file-provider, but by the 'pipeline maven' plugin: https://plugins.jenkins.io/pipeline-maven beside this, I don't think this does make a lot of sense: If you expect this to be configured on each of the pipeline jobs, then you can also just do it inside the Jenkinsfile:
withMaven(mavenSettingsConfig: 'DEFAULT_MAVEN_SETTINGS', options: [artifactsPublisher(disabled: true)]) {
sh "mvn install"
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-54872 Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Change By: Dominik Bartholdi Component/s: pipeline-maven-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54872) Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-54872 Pipeline doesnt' provide override global maven configuration option but Multibranch pipeline does Change By: Dominik Bartholdi Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54861) don't trigger initial build after branch detection
Title: Message Title Dominik Bartholdi assigned an issue to Stephen Connolly Jenkins / JENKINS-54861 don't trigger initial build after branch detection Change By: Dominik Bartholdi Assignee: Stephen Connolly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54861) don't trigger initial build after branch detection
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54861 don't trigger initial build after branch detection Issue Type: New Feature Assignee: Unassigned Components: basic-branch-build-strategies-plugin Created: 2018-11-26 14:22 Priority: Major Reporter: Dominik Bartholdi I would like to ask for a feature that would help a lot in the following scenario: we use git to promote all kind of stuff from environment to environment (some might call it GitOps or therelike) we configure/ setup jenkins fully automated and spinn up new env when ever we need to change the configuration we use 'cloudbees-bitbucket-branch-source' to monitor/ build most of our builds Now, when we spawn a new jenkins environment (because of some config changes), then 'cloudbees-bitbucket-branch-source' triggers a new initial build of all the 'master' branches too. This is a problem, as this will now cause new (unwanted) releases of some of our artifacts or even trigger an installation of the apps in a environment which is not required (because there was no actual change on the 'master' branch). What I'm asking for, is some kind of way stop some branches being automatically triggered after the scan of the organization folder. I know there are options to include/ exclude branches (even with regex), but thats not what I'm looking for - as far as I know, all the existing filters and options are to permanently exclude the branch from being build. But what we need is to be able to ensure that some branch gets only build when there is an actual change, but not when the branch was discovered during organization folder scanning.
[JIRA] (JENKINS-36442) Error after trying to view json file
Title: Message Title Dominik Bartholdi closed an issue as Cannot Reproduce Jenkins / JENKINS-36442 Error after trying to view json file Change By: Dominik Bartholdi Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46471) ERROR: Processing failed due to a bug in the code.
Title: Message Title Dominik Bartholdi closed an issue as Not A Defect Jenkins / JENKINS-46471 ERROR: Processing failed due to a bug in the code. Change By: Dominik Bartholdi Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54421) Configure page show Oops page after Installation of Artifactory Plugin
Title: Message Title Dominik Bartholdi resolved as Fixed Jenkins / JENKINS-54421 Configure page show Oops page after Installation of Artifactory Plugin Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54756) No page found 'config.jelly' for class org.jenkinsci.plugins.configfiles.GlobalConfigFiles
Title: Message Title Dominik Bartholdi resolved as Fixed Jenkins / JENKINS-54756 No page found 'config.jelly' for class org.jenkinsci.plugins.configfiles.GlobalConfigFiles Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44310) Generic fields for server credentials (Maven settings)
Title: Message Title Dominik Bartholdi commented on JENKINS-44310 Re: Generic fields for server credentials (Maven settings) Michele Vanini there is already a PR for the proxy credentials https://github.com/jenkinsci/config-file-provider-plugin/pull/53 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54576) hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder'
Title: Message Title Dominik Bartholdi commented on JENKINS-54576 Re: hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder' Mez Pahlan I commented directly on the PR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54633) build dedicated VPC while installing evergreen on AWS
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54633 build dedicated VPC while installing evergreen on AWS Issue Type: Improvement Assignee: Baptiste Mathus Components: evergreen Created: 2018-11-14 17:42 Priority: Major Reporter: Dominik Bartholdi Installing evergreen with cloudformation on AWS installs the whole thing in the default VPC. I think it would be better to isolate the build infrastructure in its own VPC. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-54576) hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder'
Title: Message Title Dominik Bartholdi commented on JENKINS-54576 Re: hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder' Mez Pahlan thanks, that works for now Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54576) hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder'
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-54576
hockeapp-plugin fails in pipeline because of missing 'baseUrlHolder'
Issue Type:
Bug
Assignee:
Mez Pahlan
Components:
hockeyapp-plugin
Created:
2018-11-12 14:32
Priority:
Critical
Reporter:
Dominik Bartholdi
I try running the following step (generated by the snippet generator):
steps {
hockeyApp applications: [
[
apiToken: 'xx',
downloadAllowed: true,
filePath: '**/app-beta.apk',
mandatory: false,
notifyTeam: false,
releaseNotesMethod: none(),
uploadMethod:
versionCreation(appId: 'yy')
]
],
debugMode: false,
failGracefully: false
}
I get the following error:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 27: Missing required parameter: "baseUrlHolder" @ line 27, column 9.
hockeyApp applications: [[apiToken: 'xx', downloadAllowed: true, filePath: '**/app-beta.apk', mandatory: false, notifyTeam: false, releaseNotesMethod: none(), uploadMethod: versionCreation(appId: 'yy')]], debugMode: false,
[JIRA] (JENKINS-39960) EC2 Plugin: Invalid groupID parameter when provisioning
Title: Message Title Dominik Bartholdi commented on JENKINS-39960 Re: EC2 Plugin: Invalid groupID parameter when provisioning sorry, forget it - I just found the missing piece - I found the field for the "Subnet ID" in the advanced settings Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39960) EC2 Plugin: Invalid groupID parameter when provisioning
Title: Message Title Dominik Bartholdi commented on JENKINS-39960 Re: EC2 Plugin: Invalid groupID parameter when provisioning Rob Birdwell Carlos Rodríguez López can you please explain exactly what you did (maybe with a screenshot)? I have the exact same problem, but I was not able to solve it so far Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54463) add JCasC pipeline step
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54463 add JCasC pipeline step Issue Type: New Feature Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin Created: 2018-11-05 14:12 Priority: Major Reporter: Dominik Bartholdi Like the job-dsl plugin [1], JCasC should also provide a pipeline step to execute/run/import configurations. This would allow us to continuously update any configuration item in Jenkins without any manual interaction (e.g. checkout configs from git and apply it to jenkins). Currently this is only possible for all stuff configurable by the job-dsl plugin. [1] https://jenkins.io/doc/pipeline/steps/job-dsl/ Add Comment
[JIRA] (JENKINS-54454) evergreen not available after restart on aws
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54454 evergreen not available after restart on aws Issue Type: Bug Assignee: R. Tyler Croy Components: evergreen Created: 2018-11-05 11:15 Priority: Minor Reporter: Dominik Bartholdi I'm running a test instance of evergreen on AWS. To see how everything works (also to see if the volume is persistent), I have stopped/started the EC2 instance. While the EC2 instance comes up, Jenkins will not come available again. Add Comment
[JIRA] (JENKINS-54447) Everyone with limited permissions can read configs
Title: Message Title Dominik Bartholdi updated JENKINS-54447 Jenkins / JENKINS-54447 Everyone with limited permissions can read configs Change By: Dominik Bartholdi Status: Fixed but Unreleased Resolved Resolution: Fixed Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54447) Everyone with limited permissions can read configs
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-54447 Re: Everyone with limited permissions can read configs I don't think this is a bug but the intention - everyone how has to having permission to create a job should also be able to see the config-files hi is able to use within his jobs. If you have files which should not be seen by everyone, then you should create folders and place the config-files within the scope of a folder where only allowed users have permission to see it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54447) Everyone with limited permissions can read configs
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-54447 Everyone with limited permissions can read configs Change By: Dominik Bartholdi Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54447) Everyone with limited permissions can read configs
Title: Message Title Dominik Bartholdi commented on JENKINS-54447 Re: Everyone with limited permissions can read configs I don't think this is a bug but the intention - everyone how has to permission to create a job should also be able to see the config-files hi is able to use within his jobs. If you have files which should not be seen by everyone, then you should create folders and place the config-files within the scope of a folder where only allowed users have permission to see it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54399) Configuration page no longer loads
Title: Message Title Dominik Bartholdi resolved as Fixed solved with 3.4.1 Jenkins / JENKINS-54399 Configuration page no longer loads Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54411) Configure page show Oops page (/configure)
Title: Message Title Dominik Bartholdi resolved as Fixed Jenkins / JENKINS-54411 Configure page show Oops page (/configure) Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54383) consider adding bitbucket-oauth and github-oauth to Evergreen
Title: Message Title Dominik Bartholdi commented on JENKINS-54383 Re: consider adding bitbucket-oauth and github-oauth to Evergreen Baptiste Mathus that really sounds like a good way for me - I'll be more than happy to do this in some kind of supporting this special flavor. For what its worth it: I currently have to move away from DEV@cloud anyway and everything I'm doing with my own instance on AWS is in the mind to be replaced by a provided solution at one day (e.g. evergreen) - this also means that I do nothing by hand anymore, everything is done with JCasC and job-dsl exclusively. So I should be able to start my seed job on any env and have the exact setup I need to do all my stuff. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54383) consider adding bitbucket-oauth and github-oauth to Evergreen
Title: Message Title Dominik Bartholdi commented on JENKINS-54383 Re: consider adding bitbucket-oauth and github-oauth to Evergreen while I do somehow understand your points, it sadly means I will have to wait even longer for evergreen to be useful for me Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54416) Configure Systems Page Showing Oops Page. Unable to Save
Title: Message Title Dominik Bartholdi resolved as Fixed unfortunate the update center was having issues while publishing the fix for this - now its released as 3.4.1 sorry for the issues it caused Jenkins / JENKINS-54416 Configure Systems Page Showing Oops Page. Unable to Save Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54396) `Configure System` page doesn't work after upgrading to 2.138.2
Title: Message Title Dominik Bartholdi resolved as Fixed unfortunate the update center was having issues while publishing the fix for this - now its released as 3.4.1 sorry for the issues it caused Jenkins / JENKINS-54396 `Configure System` page doesn't work after upgrading to 2.138.2 Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54384) consider adding pipeline-maven to essentials
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54384 consider adding pipeline-maven to essentials Issue Type: New Feature Assignee: R. Tyler Croy Components: evergreen Created: 2018-11-01 07:20 Priority: Minor Reporter: Dominik Bartholdi Please consider adding the pipeline-maven plugin to essentials. You already provide the config-file-provider plugin - the pipeline-maven plugin eases the use of settings.xml provided by the config-file-provider plugin a lot. Add Comment
[JIRA] (JENKINS-54383) consider adding bitbucket-oauth and github-oauth to essentials
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54383 consider adding bitbucket-oauth and github-oauth to essentials Issue Type: New Feature Assignee: R. Tyler Croy Components: evergreen Created: 2018-11-01 07:15 Priority: Minor Reporter: Dominik Bartholdi Evergreen already includes the multibranch plugins for github and Bitbucket I think it is just a logical consequence to also provide the ability to do authentication via the same platforms. This will also remove the need for a "local user database". Add Comment
