I put a new WAR in place and restart and normally, no issues at all. I have RedHat 6 running on an AWS EC2.
On my first try, I thought I had upgraded, but I did not realize that the version of WAR file was the same (2.263.1) I upgraded the plugins, then realized that it had not been upgraded to 2.303.1, so then I put the new WAR file in place. I was able to log in just fine, but one of the most important pipelines I have did not work. I makes a call out to Gitlab and I update Gitlab at the same time. I went backwards to snapshots I made of the two servers before I upgraded. Validated that the pipeline works, then upgraded Gitlab fully tested and the pipeline worked. So I narrowed the issue to Jenkins. I tried the upgrade again, without updating the plugins first. This time, I got an error on login page, If I clicked on Login, it gives me a prompt to put my ID and password, upon hitting enter it gives me a 403 crumb error. We use A/D to validate credentials. I have tried several times, even trying to go down to the LTS right after the 2.263 release same issue. At this point I am assuming I have a plugin problem. I tried to look at the log and even created the logging.properties file but I don't see anything glaringly obvious there either. Can someone assist, suggest something? Thank you Daniel -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1f2c0b7c-5206-48f6-80f3-ffb5a4b3d0c1n%40googlegroups.com.
