Hi Vincent, Thanks for the info. Any rough idea when is the next release 1.522 will be available? We can not downgrade, because as mentioned below the previous version of Jenkins would not work with another plugin "FindBugs". Sameh
On Wednesday, July 3, 2013 11:52:37 AM UTC-7, Vincent Latombe wrote: > Hi, > > it's JENKINS-18585, and it will be fixed in 1.522. You should > downgrade the core for the time being. > > Cheers, > > Vincent > Vincent > > > 2013/7/3 Sameh Tawfik <sta...@1fbusa.com <javascript:>>: > > Hi Lary, > > > > Thanks for your quick response. > > > > After checking all the installed plugins, it turned out "Environment > > Injector" Plugin (EnvInject Plugin) version 1.87, is the one causing > this > > problem! > > > > We need to use this plugin for all our builds, since we need to pass > > environment variables to each build. > > > > This plugin was working fine with the previous version of Jenkins > version > > 1.519? > > > > I do not see an option to install a previous version of "EnvInject" > plugin > > to see if the previous would work with the latest version of Jenkins. > > > > We need to use the newer version of Jenkins version 1.521, because the > > previous version would not work with "FindBugs" plugin. > > > > I hope this problem will be fixed in the next release of Jenkins? > > > > On Wednesday, July 3, 2013 9:33:05 AM UTC-7, Larry Shatzer, Jr. wrote: > >> > >> Check the logs when this is happening. I've had issues with some old > >> plugins in the past with similar behavior. Luckily they were plugins > that > >> were no longer used in my instance, so removal of them fixed it for me. > I'd > >> also check your javascript console for any possible errors like > >> https://issues.jenkins-ci.org/browse/JENKINS-18585 (which mentioned > some > >> plugins). > >> > >> > >> On Wed, Jul 3, 2013 at 10:26 AM, Sameh Tawfik <sta...@1fbusa.com> > wrote: > >>> > >>> > >>> > >>> Hi, > >>> > >>> We just installed Jenkins ver. 1.521, and now whenever we open any > >>> project to update some configuration by clicking on the project > configure > >>> tab, we see the first half of the configuration screen is grayed out > up to > >>> "Load script and properties files from the master" field with > "Loading" > >>> message displayed on this grayed out area, and the other half of the > project > >>> is fine, meaning it is not grayed out and we can update any field in > this > >>> area? > >>> > >>> I restarted Jenkins, but that did not make any difference! The > problem > >>> is still there! > >>> > >>> This seems to be a bug in Jenkins, because why half of the screen is > >>> grayed out, and the other have is not? > >>> > >>> Is this a new problem? Does anyone knows if there is a fix to this > >>> problem? > >>> > >>> Sameh > >>> > >>> -- > >>> 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. > >>> > >>> For more options, visit https://groups.google.com/groups/opt_out. > >>> > >>> > >> > >> > > -- > > 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 <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- 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. For more options, visit https://groups.google.com/groups/opt_out.
