Re: ResourceBundleMessageSource WARNING?

2021-03-11 Thread alan.l...@gmail.com 

Sorry for this, I believe that after upgrade to new LTS version there were 
plugins out of date.  I think running the update fixed this.
-Alan
On Thursday, March 11, 2021 at 2:25:45 PM UTC-7 alan.l...@microfocus.com 
wrote:

> I seem to have started seeing messages like the following since I updated 
> LTS to 2.277.1:
>
>  
>
> 2021-03-11 17:01:57.932+ [id=16]WARNING 
> o.s.c.s.ResourceBundleMessageSource#getResourceBundle: ResourceBundle 
> [org.acegisecurity.messages] not found for MessageSource: Can't find bundle 
> for base name org.acegisecurity.messages, locale en
>
>  
>
> Does anyone know where this comes from, or what it means?  Is this some 
> sort of upgrade issue?
>
> -Alan
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fc02e3ea-3417-40fc-a6a5-576e4bcd7986n%40googlegroups.com.

Re: 2.277.1, always upgrading

2021-03-18 Thread alan.l...@gmail.com 
So I did find the file 
"/var/lib/jenkins/jenkins.install.InstallUtil.lastExecVersion:

$ ls -l jenkins.install.InstallUtil.lastExecVersion
-rw-r--r-- 1 jenkins jenkins 7 Feb 10 19:00 
jenkins.install.InstallUtil.lastExecVersion

jenkins.install.InstallUtil.lastExecVersion:2.263.4

Note: there does not appear to be a newline after the "4".

I guess this explains the version issue, but why isn't that file updated?  
Permissions look OK
On Thursday, March 18, 2021 at 12:07:04 PM UTC-6 alan.l...@microfocus.com 
wrote:

> Something I do not recall seeing before… I have LTS Jenkins installed on 
> my Ubuntu 18.04 AWS instance.  
>
>  
>
> Every time I stop/start Jenkins, the logs say:
>
>  
>
> 2021-03-18 17:58:32.679+ [id=27]INFO
> hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last 
> running version was 2.263.4. This Jenkins is version 2.277.1.
>
> 2021-03-18 17:58:33.724+ [id=27]INFO
> hudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 
> 2.263.4 to version 2.277.1. Loaded detached plugins (and dependencies): []
>
>  
>
> And, every time, the UI shows “Jenkins 2.277.1”.   Why is this happening?  
> Where does it store the info about previous version,  to where is wants to 
> upgrade over and over?
>
>  
>
> Thanks in advance.
>
> -Alan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fb2ef7f9-1e28-42a6-a044-a98d0f27edd0n%40googlegroups.com.

Re: 2.277.1, always upgrading

2021-04-20 Thread alan.l...@gmail.com 
I commented on that ticket, issue is still open and apparent with 2.277.3.
On Sunday, April 11, 2021 at 6:34:42 AM UTC-6 Mark Waite wrote:

> Thanks!  Daniel Beck logged https://issues.jenkins.io/browse/JENKINS-65329 
> to track the changes needed to fix that issue.
>
> On Sun, Apr 11, 2021 at 6:31 AM Steve Bouché  wrote:
>
>> I'm following LTS as well and have been seeing this issue.  It started 
>> happening on my upgrade from v2.263.4 to 2.277.1, and happened again on my 
>> upgrade from v2.277.1 to 2.277.2.
>> My setup is using the jenkins/jenkins Docker image.
>>
>> 2021-04-09 04:55:10.282+ [id=27] INFO 
>> hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last 
>> running version was 2.263.4. This Jenkins is version 2.277.2. 
>>
>> 2021-04-01 06:17:43.714+ [id=26] INFO 
>> hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last 
>> running version was 2.263.4. This Jenkins is version 2.277.1.
>>
>> 2021-02-10 21:59:54.968+ [id=27] INFO 
>> hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last 
>> running version was 2.263.2. This Jenkins is version 2.263.4.
>>
>> $ stat jenkins.install.InstallUtil.lastExecVersion
>>   File: jenkins.install.InstallUtil.lastExecVersion
>>   Size: 7   Blocks: 8  IO Block: 1048576 regular file
>> Device: b3h/179dInode: 17206725611182888295  Links: 1
>> Access: (0644/-rw-r--r--)  Uid: ( 1000/ jenkins)   Gid: ( 1000/ jenkins)
>> Access: 2021-02-24 18:30:06.69600 +
>> Modify: 2021-02-24 18:30:06.69600 +
>> Change: 2021-02-24 18:30:06.69600 +
>>  Birth: -
>> $ cat -Env jenkins.install.InstallUtil.lastExecVersion
>>  1  2.263.4
>>
>> It doesn't seem to be affecting anything.  Happy to provide more 
>> information to anyone interested.
>>
>> Thanks!
>> Steve
>>
>> On Thursday, March 18, 2021 at 11:28:48 AM UTC-7 alan.l...@gmail.com 
>> wrote:
>>
>>> So I did find the file 
>>> "/var/lib/jenkins/jenkins.install.InstallUtil.lastExecVersion:
>>>
>>> $ ls -l jenkins.install.InstallUtil.lastExecVersion
>>> -rw-r--r-- 1 jenkins jenkins 7 Feb 10 19:00 
>>> jenkins.install.InstallUtil.lastExecVersion
>>>
>>> jenkins.install.InstallUtil.lastExecVersion:2.263.4
>>>
>>> Note: there does not appear to be a newline after the "4".
>>>
>>> I guess this explains the version issue, but why isn't that file 
>>> updated?  Permissions look OK
>>> On Thursday, March 18, 2021 at 12:07:04 PM UTC-6 
>>> alan.l...@microfocus.com wrote:
>>>
>>>> Something I do not recall seeing before… I have LTS Jenkins installed 
>>>> on my Ubuntu 18.04 AWS instance.  
>>>>
>>>>  
>>>>
>>>> Every time I stop/start Jenkins, the logs say:
>>>>
>>>>  
>>>>
>>>> 2021-03-18 17:58:32.679+ [id=27]INFO
>>>> hudson.PluginManager#loadDetachedPlugins: Upgrading Jenkins. The last 
>>>> running version was 2.263.4. This Jenkins is version 2.277.1.
>>>>
>>>> 2021-03-18 17:58:33.724+ [id=27]INFO
>>>> hudson.PluginManager#loadDetachedPlugins: Upgraded Jenkins from version 
>>>> 2.263.4 to version 2.277.1. Loaded detached plugins (and dependencies): []
>>>>
>>>>  
>>>>
>>>> And, every time, the UI shows “Jenkins 2.277.1”.   Why is this 
>>>> happening?  Where does it store the info about previous version,  to where 
>>>> is wants to upgrade over and over?
>>>>
>>>>  
>>>>
>>>> Thanks in advance.
>>>>
>>>> -Alan
>>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/d150c431-47f8-4268-914c-d8dad1f0f886n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/d150c431-47f8-4268-914c-d8dad1f0f886n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4ad1ddc3-91ec-4fa1-9ff9-8cc5c2514af5n%40googlegroups.com.

Re: SAML plugin 2.0.8

2021-08-31 Thread alan.l...@gmail.com 
Sounds good, and the security warning did clear.  Thanks for the rapid 
response!
-Alan

On Tuesday, August 31, 2021 at 10:53:27 AM UTC-6 db...@cloudbees.com wrote:

> On Tue, Aug 31, 2021 at 5:29 PM Alan Sparks  
> wrote:
>
>> I went to upgrade this, and the after-installed one shows the same 
>> security notice in my Jenkins 2.289.3 master.  The GitHub Releases shows 
>> 2.0.7 as the current.  Was the 2.0.8 release pulled back?
>>
>> -Alan
>>
>
> The release has not been pulled. Two separate issues here:
>
> - Release drafter / GH releases do not play well with how we prepare and 
> publish security updates. A maintainer will need to manually create the 
> release on GH.
> - I published wrong security warnings at first and fixed them ~15 minutes 
> ago. If 2.0.8 is installed, they should disappear once you refresh 
> update center metadata.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e5db2ca6-1d5e-4895-8693-5a78ac90b500n%40googlegroups.com.

Re: Jenkins stable 2.319.1?

2021-12-01 Thread alan.l...@gmail.com 
I guess I'm paranoid.  I guess the release came out before the changelog.  
Sorry for the interruption.

On Wednesday, December 1, 2021 at 11:24:43 AM UTC-7 
alan.l...@microfocus.com wrote:

> I got a notice on Jenkins of a new stable release 2.319.1.  And it’s in 
> the //pkg.jenkins.io/debian-stable repo.  But see no changelog for it and 
> didn’t see a pre-notice in announcements.   Is this real?
>
> -Alan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a18064f5-330e-4176-974e-92dcf48bcdfcn%40googlegroups.com.

Support for CloudBees plugins

2022-01-13 Thread alan.l...@gmail.com 
For last 2 weeks, been trying to get attention on bug with CloudBees AWS 
credentials plugin 1.33.   The external ID feature causes failures for 
anything using an AWS role without an external ID.

I can't seem to get a response on this problem (looks like others have 
issues too).  Is there a process besides opening a ticket and waiting?

Issue on Jenkins JIRA:
https://issues.jenkins.io/browse/JENKINS-67452

Issue on GitHub:
https://github.com/jenkinsci/aws-credentials-plugin/issues/116

Thanks for any advice.
-Alan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/be6909de-b449-4d02-8c0f-8042bbe7299an%40googlegroups.com.

Re: CloudBees AWS creds plugin 1.33 issues

2022-01-11 Thread alan.l...@gmail.com 
Bump... Has anyone had any success with this?  I created a JIRA, but no 
responses.  Also no responses on the Github issue 
(https://github.com/jenkinsci/aws-credentials-plugin/issues/116).  Thanks 
for any advice.

On Thursday, January 6, 2022 at 9:55:10 AM UTC-7 alan.l...@microfocus.com 
wrote:

> I did an update on my test Jenkins instance, which included updates to the 
> CloudBees AWS credentials plugin.  Doesn’t seem that the EC2 Fleet plugin 
> was part of that update, but not I have a big problem…
>
>  
>
> I’m getting this over and over in the logs, below.  Appears to be caused 
> by an issue in the new “externalID” code in the creds plugin.  I’ve opened 
> a bug on JIRA (JENKINS-67452).  Seems to be a similar but different issue 
> reported in GitHub project (issue 116).  Hoping this gets fixed soon.  
>
>  
>
> Update:  Don’t seem to be getting any attention on the Jira for this.  
> It’s been 20 days.  Anyone know a workaround?
>
> -Alan
>
>  
>
>  
>
> 2021-12-24 19:19:53.568+ [id=32]INFO
> c.a.jenkins.ec2fleet.CloudNanny#doRun: Error during fleet 'FleetCloud' 
> stats update
>
> com.amazonaws.services.securitytoken.model.AWSSecurityTokenServiceException: 
> 1 validation error detected: Value '' at 'externalId' failed to satisfy 
> constraint: Member must have length greater than or equal to 2 (Service: 
> AWSSecurityTokenService; Status Code: 400; Error Code: ValidationError; 
> Request ID: a50581d4-050c-4601-81ad-18184a9293be; Proxy: null)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1862)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleServiceErrorResponse(AmazonHttpClient.java:1415)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1384)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1154)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:811)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:779)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:753)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:713)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:695)
>
> at 
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:559)
>
> at 
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:539)
>
> at 
> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.doInvoke(AWSSecurityTokenServiceClient.java:1682)
>
> at 
> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.invoke(AWSSecurityTokenServiceClient.java:1649)
>
> at 
> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.invoke(AWSSecurityTokenServiceClient.java:1638)
>
> at 
> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.executeAssumeRole(AWSSecurityTokenServiceClient.java:498)
>
> at 
> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.assumeRole(AWSSecurityTokenServiceClient.java:467)
>
> at 
> com.cloudbees.jenkins.plugins.awscredentials.AWSCredentialsImpl.getCredentials(AWSCredentialsImpl.java:161)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.getCredentialsFromContext(AmazonHttpClient.java:1266)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.runBeforeRequestHandlers(AmazonHttpClient.java:842)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:792)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:779)
>
>at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:753)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:713)
>
> at 
> com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:695)
>
> at 
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:559)
>
> at 
> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:539)
>
> at 
> com.amazonaws.services.autoscaling.AmazonAutoScalingClient.doInvoke(AmazonAutoScalingClient.java:4931)
>
> at 
> com.amazonaws.services.autoscaling.AmazonAutoScalingClient.invoke(AmazonAutoScalingClient.java:4898)
>
> at 
> com.amazonaws.services.autoscaling.AmazonAutoScalingClient.invoke(AmazonAutoScalingClient.java:4887)
>
> at 
> com.amazonaws.services.autoscaling.AmazonAutoScalingClient.executeDescribeAutoScalingGroups(AmazonAutoScalingClient.java:1847)
>
> at 
>

Re: CloudBees AWS creds plugin 1.33 issues

2022-01-11 Thread alan.l...@gmail.com 
To add more information, I've determined that for my case (using the 
ec2-fleet plugin), I need to add a dummy value to the CloudBees AWS 
credential (like 'xx') advanced external-id configuration.  If I put that 
there, I can run.  If I take it back out, I start getting continuous errors 
from the credentials plugin.

On Tuesday, January 11, 2022 at 9:14:04 AM UTC-7 alan.l...@gmail.com wrote:

> Bump... Has anyone had any success with this?  I created a JIRA, but no 
> responses.  Also no responses on the Github issue (
> https://github.com/jenkinsci/aws-credentials-plugin/issues/116).  Thanks 
> for any advice.
>
> On Thursday, January 6, 2022 at 9:55:10 AM UTC-7 alan.l...@microfocus.com 
> wrote:
>
>> I did an update on my test Jenkins instance, which included updates to 
>> the CloudBees AWS credentials plugin.  Doesn’t seem that the EC2 Fleet 
>> plugin was part of that update, but not I have a big problem…
>>
>>  
>>
>> I’m getting this over and over in the logs, below.  Appears to be caused 
>> by an issue in the new “externalID” code in the creds plugin.  I’ve opened 
>> a bug on JIRA (JENKINS-67452).  Seems to be a similar but different issue 
>> reported in GitHub project (issue 116).  Hoping this gets fixed soon.  
>>
>>  
>>
>> Update:  Don’t seem to be getting any attention on the Jira for this.  
>> It’s been 20 days.  Anyone know a workaround?
>>
>> -Alan
>>
>>  
>>
>>  
>>
>> 2021-12-24 19:19:53.568+ [id=32]INFO
>> c.a.jenkins.ec2fleet.CloudNanny#doRun: Error during fleet 'FleetCloud' 
>> stats update
>>
>> com.amazonaws.services.securitytoken.model.AWSSecurityTokenServiceException: 
>> 1 validation error detected: Value '' at 'externalId' failed to satisfy 
>> constraint: Member must have length greater than or equal to 2 (Service: 
>> AWSSecurityTokenService; Status Code: 400; Error Code: ValidationError; 
>> Request ID: a50581d4-050c-4601-81ad-18184a9293be; Proxy: null)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1862)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleServiceErrorResponse(AmazonHttpClient.java:1415)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1384)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1154)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:811)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:779)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:753)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:713)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:695)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:559)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:539)
>>
>> at 
>> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.doInvoke(AWSSecurityTokenServiceClient.java:1682)
>>
>> at 
>> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.invoke(AWSSecurityTokenServiceClient.java:1649)
>>
>> at 
>> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.invoke(AWSSecurityTokenServiceClient.java:1638)
>>
>> at 
>> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.executeAssumeRole(AWSSecurityTokenServiceClient.java:498)
>>
>> at 
>> com.amazonaws.services.securitytoken.AWSSecurityTokenServiceClient.assumeRole(AWSSecurityTokenServiceClient.java:467)
>>
>> at 
>> com.cloudbees.jenkins.plugins.awscredentials.AWSCredentialsImpl.getCredentials(AWSCredentialsImpl.java:161)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.getCredentialsFromContext(AmazonHttpClient.java:1266)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.runBeforeRequestHandlers(AmazonHttpClient.java:842)
>>
>> at 
>> com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:792)
>>
>> at 
>> com.amazonaws.http.AmazonHtt

Re: Support for CloudBees plugins

2022-01-31 Thread alan.l...@gmail.com 
I do understand that CloudBees is probably quite busy... but you have to 
note this issue has been open on both GitHub and the Jenkins JIRA for over 
a month without anyone acknowledging it or taking ownership.   I understand 
the correct action for subscribers is mostly "just don't upgrade,"  but it 
would be nice if the tickets could be acknowledged.
-Alan

On Friday, January 21, 2022 at 6:31:06 AM UTC-7 bma...@gmail.com wrote:

> Hi,
>
> While our teams are aware of this issue and we should look into it soon 
> enough, I can't commit to any precise date. In particular in this case 
> because the workaround is easy: going back to 1.32 AFAIU.
> Many other more pressing priorities are higher than this (e.g. making sure 
> the hundreds of plugins, many OSS, that CloudBees verifies 
> <https://docs.cloudbees.com/docs/admin-resources/latest/assurance-program/> 
> are ready for the next LTS).
>
> I would say there are 3 options:
>
>- Wait until somebody picks it up.
>- File the fix yourself (or someone in your company, or paying someone 
>to do it), then we can probably try and fast track the merge & release for 
>it.
>- for CloudBees customers only: use ZenDesk to discuss further 
>options. 
>
> Hope this helps clarify.
>
> Le mer. 19 janv. 2022 à 19:44, alan.l...@gmail.com  
> a écrit :
>
>> Appears that no one at CloudBees has looked at the issue with the AWS 
>> Credentials plugin.  The issue is over a month old.  Is there a contact at 
>> CloudBees I could ping to find out options?   Thanks.
>> -Alan
>>
>> On Thursday, January 13, 2022 at 2:37:20 PM UTC-7 
>> alan.l...@microfocus.com wrote:
>>
>>> Frankly I don’t have any experience doing this… so any help would be 
>>> appreciated.  Thanks for the reply!
>>>
>>> -Alan
>>>
>>>  
>>>
>>> *From:* jenkins...@googlegroups.com  *On 
>>> Behalf Of *Baptiste Mathus
>>> *Sent:* Thursday, January 13, 2022 2:27 PM
>>> *To:* jenkins...@googlegroups.com
>>> *Subject:* Re: Support for CloudBees plugins
>>>
>>>  
>>>
>>> Hi, 
>>>
>>> Thanks for the notice. Reporting the bug in Jira is the right way indeed.
>>>
>>> I know nothing about this plugin myself, but looking around in the last 
>>> changes, it looks like 
>>> https://github.com/jenkinsci/aws-credentials-plugin/pull/88/files#r772008354
>>>  
>>> could be a good lead.
>>>
>>>  
>>>
>>> I would recommend creating a PR with something around this. The build 
>>> will then automatically create an "incremental" and allow you to test this 
>>> to help fix it. Doing it would be invaluable to at least identify the exact 
>>> cause for your issue.
>>>
>>>  
>>>
>>> If you do not know how to do it, I *might* give it a look later this 
>>> week or next one, but no guarantee.
>>>
>>>  
>>>
>>> Cheers
>>>
>>>  
>>>
>>> Le jeu. 13 janv. 2022 à 21:39, alan.l...@gmail.com  
>>> a écrit :
>>>
>>> For last 2 weeks, been trying to get attention on bug with CloudBees AWS 
>>> credentials plugin 1.33.   The external ID feature causes failures for 
>>> anything using an AWS role without an external ID.
>>>
>>>  
>>>
>>> I can't seem to get a response on this problem (looks like others have 
>>> issues too).  Is there a process besides opening a ticket and waiting?
>>>
>>>  
>>>
>>> Issue on Jenkins JIRA:
>>>
>>> https://issues.jenkins.io/browse/JENKINS-67452
>>>
>>>  
>>>
>>> Issue on GitHub:
>>>
>>> https://github.com/jenkinsci/aws-credentials-plugin/issues/116
>>>
>>>  
>>>
>>> Thanks for any advice.
>>>
>>> -Alan
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/be6909de-b449-4d02-8c0f-8042bbe7299an%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/be6909de-b449-4d02-8c0f-8042bbe7299an%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>> -- 
>>> You rec

Re: Support for CloudBees plugins

2022-01-19 Thread alan.l...@gmail.com 
Appears that no one at CloudBees has looked at the issue with the AWS 
Credentials plugin.  The issue is over a month old.  Is there a contact at 
CloudBees I could ping to find out options?   Thanks.
-Alan

On Thursday, January 13, 2022 at 2:37:20 PM UTC-7 alan.l...@microfocus.com 
wrote:

> Frankly I don’t have any experience doing this… so any help would be 
> appreciated.  Thanks for the reply!
>
> -Alan
>
>  
>
> *From:* jenkins...@googlegroups.com  *On 
> Behalf Of *Baptiste Mathus
> *Sent:* Thursday, January 13, 2022 2:27 PM
> *To:* jenkins...@googlegroups.com
> *Subject:* Re: Support for CloudBees plugins
>
>  
>
> Hi, 
>
> Thanks for the notice. Reporting the bug in Jira is the right way indeed.
>
> I know nothing about this plugin myself, but looking around in the last 
> changes, it looks like 
> https://github.com/jenkinsci/aws-credentials-plugin/pull/88/files#r772008354 
> could be a good lead.
>
>  
>
> I would recommend creating a PR with something around this. The build will 
> then automatically create an "incremental" and allow you to test this to 
> help fix it. Doing it would be invaluable to at least identify the exact 
> cause for your issue.
>
>  
>
> If you do not know how to do it, I *might* give it a look later this week 
> or next one, but no guarantee.
>
>  
>
> Cheers
>
>  
>
> Le jeu. 13 janv. 2022 à 21:39, alan.l...@gmail.com  
> a écrit :
>
> For last 2 weeks, been trying to get attention on bug with CloudBees AWS 
> credentials plugin 1.33.   The external ID feature causes failures for 
> anything using an AWS role without an external ID.
>
>  
>
> I can't seem to get a response on this problem (looks like others have 
> issues too).  Is there a process besides opening a ticket and waiting?
>
>  
>
> Issue on Jenkins JIRA:
>
> https://issues.jenkins.io/browse/JENKINS-67452
>
>  
>
> Issue on GitHub:
>
> https://github.com/jenkinsci/aws-credentials-plugin/issues/116
>
>  
>
> Thanks for any advice.
>
> -Alan
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/be6909de-b449-4d02-8c0f-8042bbe7299an%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/be6909de-b449-4d02-8c0f-8042bbe7299an%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6XAJQKwRpNJPjzuH5BK4B-H6sWqS4a7nfbr0_AtpA7cA%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6XAJQKwRpNJPjzuH5BK4B-H6sWqS4a7nfbr0_AtpA7cA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/90f76464-31c7-411e-a0fe-9b8422a2f710n%40googlegroups.com.

Re: 500: Response header too large

2023-10-20 Thread alan.l...@gmail.com 
Sorry to bump, but any ideas?  I get the stacktrace hitting the logout link 
and a white page, but it never actually logs out.  A back button press puts 
me back logged into Jenkins.

On Thursday, October 19, 2023 at 11:17:45 AM UTC-6 alan.l...@gmail.com 
wrote:

> Meant to add the stack trace.  See attached text file.
>
> On Thursday, October 19, 2023 at 10:53:54 AM UTC-6 alan.l...@gmail.com 
> wrote:
>
>> I'm trying to upgrade a Jenkins server from 2.401 to 2.414.3.  All seems 
>> OK except I notice the "logout" link throws a blank page, and a stacktrace 
>> with the following:
>>
>> https://jenkins-test.xxx.xxx.com/logout
>> org.eclipse.jetty.http.BadMessageException: 500: Response header too large
>>
>> I can find things about request header size, but changing that doesn't 
>> help.  Can anyone suggest a place to look for the cause of this?  What 
>> information is needed to debug it?
>>
>> This is the new Jenkins 2.414.3 LTS, running on 
>> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, 
>> mixed mode, sharing)
>>
>> Thanks in advance.
>> -Alan
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/da4910b1-b15e-4ad6-96ee-b8b9d16ead32n%40googlegroups.com.

500: Response header too large

2023-10-19 Thread alan.l...@gmail.com 
I'm trying to upgrade a Jenkins server from 2.401 to 2.414.3.  All seems OK 
except I notice the "logout" link throws a blank page, and a stacktrace 
with the following:

https://jenkins-test.xxx.xxx.com/logout
org.eclipse.jetty.http.BadMessageException: 500: Response header too large

I can find things about request header size, but changing that doesn't 
help.  Can anyone suggest a place to look for the cause of this?  What 
information is needed to debug it?

This is the new Jenkins 2.414.3 LTS, running on 
OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, 
mixed mode, sharing)

Thanks in advance.
-Alan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/91f996ca-d957-499e-98b9-16dddaea20dcn%40googlegroups.com.

Re: 500: Response header too large

2023-10-19 Thread alan.l...@gmail.com 
Meant to add the stack trace.  See attached text file.

On Thursday, October 19, 2023 at 10:53:54 AM UTC-6 alan.l...@gmail.com 
wrote:

> I'm trying to upgrade a Jenkins server from 2.401 to 2.414.3.  All seems 
> OK except I notice the "logout" link throws a blank page, and a stacktrace 
> with the following:
>
> https://jenkins-test.xxx.xxx.com/logout
> org.eclipse.jetty.http.BadMessageException: 500: Response header too large
>
> I can find things about request header size, but changing that doesn't 
> help.  Can anyone suggest a place to look for the cause of this?  What 
> information is needed to debug it?
>
> This is the new Jenkins 2.414.3 LTS, running on 
> OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu118.04.1, 
> mixed mode, sharing)
>
> Thanks in advance.
> -Alan
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ea4cdb0c-b214-4f51-a3c3-93d4f48f0446n%40googlegroups.com.
2023-10-19 16:31:11.421+ [id=17]WARNING 
o.e.j.s.h.ContextHandler$Context#log: Error while serving 
https://jenkins-test.xxx.com/logout
org.eclipse.jetty.http.BadMessageException: 500: Response header too large
at 
org.eclipse.jetty.server.HttpConnection$SendCallback.process(HttpConnection.java:774)
at 
org.eclipse.jetty.util.IteratingCallback.processing(IteratingCallback.java:243)
at 
org.eclipse.jetty.util.IteratingCallback.iterate(IteratingCallback.java:224)
at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:589)
at 
org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:1046)
at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:1123)
at org.eclipse.jetty.server.HttpOutput.channelWrite(HttpOutput.java:270)
at org.eclipse.jetty.server.HttpOutput.close(HttpOutput.java:623)
at org.eclipse.jetty.server.Response.closeOutput(Response.java:980)
at org.eclipse.jetty.server.Response.sendRedirect(Response.java:614)
at org.eclipse.jetty.server.Response.sendRedirect(Response.java:545)
at org.eclipse.jetty.server.Response.sendRedirect(Response.java:620)
at 
javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:130)
at 
javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:130)
at 
org.springframework.security.web.util.OnCommittedResponseWrapper.sendRedirect(OnCommittedResponseWrapper.java:136)
at 
javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:130)
at 
javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:130)
at org.kohsuke.stapler.ResponseImpl.sendRedirect(ResponseImpl.java:142)
at org.kohsuke.stapler.ResponseImpl.sendRedirect2(ResponseImpl.java:158)
at hudson.security.SecurityRealm.doLogout(SecurityRealm.java:334)
at jenkins.model.Jenkins.doLogout(Jenkins.java:4371)
at 
java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:397)
Caused: java.lang.reflect.InvocationTargetException
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:401)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:409)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:207)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:140)
at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:558)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:59)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:770)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:900)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:698)
at org.kohsuke.stapler.Stapler.service(Stapler.java:248)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:590)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764)
at 
org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1665)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:163)
at 
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:114)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:160)
at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:160)

Re: 500: Response header too large

2023-10-23 Thread alan.l...@gmail.com 
Thanks very much for the response.  You are correct, clearing the cache 
solved that issue.
-Alan

On Monday, October 23, 2023 at 6:40:27 AM UTC-6 db...@cloudbees.com wrote:

> On Fri, Oct 20, 2023 at 8:38 PM alan.l...@gmail.com  
> wrote:
>
>> Sorry to bump, but any ideas?  I get the stacktrace hitting the logout 
>> link and a white page, but it never actually logs out.  A back button press 
>> puts me back logged into Jenkins.
>>
>
> The logout attempts to clear cookies as they can accumulate after many 
> restarts/updates, each time with a different ID. I guess it's possible that 
> your requests (with a huge Cookie header) are fine, but the response, 
> trying to clear them all out, is not.
> Diagnose by checking what your Cookie request header is, I expect you send 
> dozens of session cookies.
> Try login/logout from a private browsing window, if that works it's an 
> indicator your cookies are a problem.
> If so, temporarily resolve this issue by clearing browsing data in your 
> browser (and use the logout more often).
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/15fb31e5-c908-433d-98fe-ca7c2b6ec198n%40googlegroups.com.

Jenkins LTS Debian signing key?

2023-03-30 Thread alan.l...@gmail.com 
Tried to build a Jenkins image here this morning and getting signing errors 
on the repo:

W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
https://pkg.jenkins.io/debian-stable binary/ Release: The following 
signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins Project 

W: Failed to fetch http://pkg.jenkins.io/debian-stable/binary/Release.gpg 
 The following signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins 
Project 
W: Some index files failed to download. They have been ignored, or old ones 
used instead.

I see a post on the Jenkins blog about the key changing, but it says April 
5, and we're not then yet.  What has changed for Ubuntu users?  the old key 
doesn't seem to work, nor does the new one.  I'm using the same repo 
configuration:
deb https://pkg.jenkins.io/debian-stable binary/

What has changed?

Following instructions for 2.387.1at:
https://www.jenkins.io/doc/book/installing/linux/#long-term-support-release

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/54ae60e4-9408-482f-844d-5abb50abc4den%40googlegroups.com.

Re: Jenkins LTS Debian signing key?

2023-03-30 Thread alan.l...@gmail.com 
Thanks.  I'll disable the checks and wait for the release.  Thanks for the 
info.


On Thursday, March 30, 2023 at 11:44:11 AM UTC-6 Mark Waite wrote:

> On Thursday, March 30, 2023 at 11:13:20 AM UTC-6 Alan Sparks wrote:
>
> Tried to build a Jenkins image here this morning and getting signing 
> errors on the repo:
>
> W: An error occurred during the signature verification. The repository is 
> not updated and the previous index files will be used. GPG error: 
> https://pkg.jenkins.io/debian-stable binary/ Release: The following 
> signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins Project
>
> W: Failed to fetch http://pkg.jenkins.io/debian-stable/binary/Release.gpg 
>  The following signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins 
> Project
>
> W: Some index files failed to download. They have been ignored, or old 
> ones used instead.
>
>
> I see a post on the Jenkins blog about the key changing, but it says April 
> 5, and we're not then yet.  What has changed for Ubuntu users?  the old key 
> doesn't seem to work, nor does the new one.  I'm using the same repo 
> configuration:
> deb https://pkg.jenkins.io/debian-stable binary/
>
> What has changed?
>
>
> The GPG private key that signs the Jenkins 2.387.1 deb file expired March 
> 30, 2023.  A comment 
> 
>  
> to the blog post 
>  
> says:
>
> > Users installing Jenkins LTS 2.387.1 after March 31, 2023 may see a 
> warning or an error noting that the PGP key has expired.
>
> > Jenkins LTS 2.387.2 (April 5, 2023) will resolve that warning, so long 
> as the new PGP public key has been installed by following the instructions 
> in the Linux installation page 
> 
> You're correct that the old key does not work (because it has expired) and 
> that the new key does not work with the old releases (because they were not 
> signed with the new key). 
>
> The new key works with new releases (like Jenkins 2.397 released March 28, 
> 2023 and Jenkins 2.387.2 that will be released April 5, 2023).
>
> If you need to install Jenkins LTS with the Linux installer between now 
> and April 5, your choices include:
>
>- Override the package manager to ignore the expired PGP key
>- Use a container image like jenkins/jenkins:2.387.1-jdk11 
>
> 
>- Install the war file without the Linux installer
>
> Mark Waite
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/862e7b7f-5d75-4cbe-92bf-69e058a1fbc7n%40googlegroups.com.

Re: Jenkins plugin role-strategy and CasC breakage

2023-07-10 Thread alan.l...@gmail.com 
 

I see that a ticket was opened for this already, with a workaround:

https://issues.jenkins.io/browse/JENKINS-71612

 

Sorry for the noise.

-Alan


On Monday, July 10, 2023 at 11:52:08 AM UTC-6 alan.l...@gmail.com wrote:

> I see that the newer role-strategy plugin (including and after version 
> 657.v398b_8a_279c49 
> <https://updates.jenkins.io/download/plugins/role-strategy/657.v398b_8a_279c49/role-strategy.hpi>)
>  
> is marked as potentially incompatible.  Other than the pointer to 
> JENKINS-68755 <https://issues.jenkins.io/browse/JENKINS-68755>, I can't 
> find exactly what the break is (and I'm not seeing it from that ticket).
>
> But upgrading it does break Jenkins with my CasC configuration, with some 
> incompatibility to the original config language:
>
> io.jenkins.plugins.casc.ConfiguratorException: 'assignments' is deprecated
> at 
> io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:330)
> at 
> io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:283)
> at 
> io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:81)
> at 
> io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:156)
> at 
> io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:75)
> at 
> io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:274)
> at 
> io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:81)
> at 
> org.jenkinsci.plugins.rolestrategy.casc.RoleBasedAuthorizationStrategyConfigurator.instance(RoleBasedAuthorizationStrategyConfigurator.java:58)
> at 
> org.jenkinsci.plugins.rolestrategy.casc.RoleBasedAuthorizationStrategyConfigurator.instance(RoleBasedAuthorizationStrategyConfigurator.java:34)
> at 
> io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:274)
>
> The first part of my CasC config that used to work is:
>   authorizationStrategy:
> roleBased:
>   roles:
> global:
> - assignments:
>   - "ccoe_svc_jenkinsapi"
>   - "IS_CCOE"
>   - "PSec_Admins"
>
> I can't find the info on what changed and how that affects CasC going 
> forward.  Does anyone know the location of docs that include the 
> workarounds?  Thanks.
> -Alan
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f42a5995-cec2-4052-b051-0bab505e238cn%40googlegroups.com.

Jenkins plugin role-strategy and CasC breakage

2023-07-10 Thread alan.l...@gmail.com 
I see that the newer role-strategy plugin (including and after version 
657.v398b_8a_279c49 
)
 
is marked as potentially incompatible.  Other than the pointer to 
JENKINS-68755 , I can't 
find exactly what the break is (and I'm not seeing it from that ticket).

But upgrading it does break Jenkins with my CasC configuration, with some 
incompatibility to the original config language:

io.jenkins.plugins.casc.ConfiguratorException: 'assignments' is deprecated
at 
io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:330)
at 
io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:283)
at 
io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:81)
at 
io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:156)
at 
io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:75)
at 
io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:274)
at 
io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.configure(DataBoundConfigurator.java:81)
at 
org.jenkinsci.plugins.rolestrategy.casc.RoleBasedAuthorizationStrategyConfigurator.instance(RoleBasedAuthorizationStrategyConfigurator.java:58)
at 
org.jenkinsci.plugins.rolestrategy.casc.RoleBasedAuthorizationStrategyConfigurator.instance(RoleBasedAuthorizationStrategyConfigurator.java:34)
at 
io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:274)

The first part of my CasC config that used to work is:
  authorizationStrategy:
roleBased:
  roles:
global:
- assignments:
  - "ccoe_svc_jenkinsapi"
  - "IS_CCOE"
  - "PSec_Admins"

I can't find the info on what changed and how that affects CasC going 
forward.  Does anyone know the location of docs that include the 
workarounds?  Thanks.
-Alan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/86951a33-ed00-473c-8f75-da10d010e953n%40googlegroups.com.

Jenkins 2.246.2 - lost build "parameters" menu item

2024-01-22 Thread alan.l...@gmail.com 
I have a couple of Jenkins instances running 2.246.2.  I configure both 
from an AMI that includes a JCasC YAML file to set role permissions and 
assignments.

I noticed today that, on a build page, the "parameters" left menu item is 
missing.  The funny thing is that it appears on the other Jenkins instance, 
same Jenkins version, same Java, same Jenkins.yaml for the JCasC config.

Am I missing a permission somewhere?  Is there a permission that controls 
whether the "parameters" menu item appears on a page?

Thanks for any guidance.
-Alan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4fd3f524-94d4-46ed-ae44-b6d53aeded68n%40googlegroups.com.

Re: Need IP address of Jenkins

2024-02-22 Thread alan.l...@gmail.com 
This looks like you're asking for information from us that is private and 
specific for your company.  We can't provide information on your IP 
addresses or configuration.  You need to reach out to whomever manages your 
Jenkins server at your company.

On Thursday, February 22, 2024 at 7:56:40 AM UTC-7 surabhivi...@gmail.com 
wrote:

> Hello team,
>
> Please consider it as *urgent *and guide me to whom I have to reach out 
> for this.
> Surabhi
>
> On Wednesday, February 21, 2024 at 1:03:04 PM UTC+5:30 surabhi vinchurkar 
> wrote:
>
>> Hello Team,
>>
>> Waiting for your response.
>>
>> Thank you
>>
>> On Tuesday, February 20, 2024 at 7:10:21 PM UTC+5:30 surabhi vinchurkar 
>> wrote:
>>
>>> Hi Team,
>>>
>>>  
>>>
>>> We are trying to migrate the Flosum Pipeline (with Jenkins WebHook for 
>>> Selenium scripts) setup from Azure to AWS machine.
>>>
>>> The Setup is working fine in the Azure machine and we need to do the 
>>> same setup in AWS machine. But we are getting the below error in AWS. 
>>> We recently changed the Jenkins URL from HTTP to HTTPS.
>>>
>>> Error message: System.CalloutException: Read timed out
>>>
>>>  
>>>
>>> I have whitelisted Salesforce IP addresses for inbound rule. But for 
>>> outbound rule, required Salesforce IP addresses and Jenkins IP addresses.
>>>
>>>  
>>>
>>> *Requesting you to provide me the list of Jenkins IP addresses and port. 
>>> *(For setup I have used port 8080 and 8443)
>>>
>>>  
>>>
>>> Note: The inbound rule specifies from where the server can be accessed. 
>>> The outbound configuration determines where the server can obtain access. 
>>> In the inbound rule you should have Salesforce IP addresses, and in the 
>>> outbound rule you should have Salesforce IP addresses and Jenkins IP 
>>> addresses.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/51d4c0b3-6872-466a-8955-eab3b2bae190n%40googlegroups.com.