Jenkins 2.204.3 LTS RC testing started

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Jenkins 2.204.3 LTS RC testing started

Oliver Gondža-2
Hello everyone,

Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-02-26.

Please, report your findings in this thread.

Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war

Thanks!
--
oliver

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c39ac777-ee73-66ad-1b62-9fc473aae342%40gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.204.3 LTS RC testing started

Mark Waite-2


On Friday, February 14, 2020 at 5:05:22 AM UTC-7, ogondza wrote:
Hello everyone,

Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-02-26.

Please, report your findings in this thread.


I've encountered a problem on my Jenkins test instances that are running the 2.204.3 release candidate inside Docker.  Some of the folders fail to open when I click them and I receive the following stack track in an "Oops" page on one instance:

org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.204.3-SNAPSHOT.jar!/hudson/model/View/index.jelly:42:43: <st:include> org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.204.3-SNAPSHOT.jar!/lib/hudson/projectView.jelly:84:48: <j:forEach> java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
	at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)

In the other test instance, the message appears in the console log and does not appear in the Jenkins Oops page.  In the console log, it reports:

2020-02-15 16:37:04.540+0000 [id=164374]        INFO    j.b.MultiBranchProject$BranchIndexing#run: Bugs-Pipeline-Checks/jenkins-bugs-multibranch-pipeline-bitbucket #20200215.093700 branch indexing action completed: SUCCESS in 3.6 sec
2020-02-15 16:39:26.329+0000 [id=39]    SEVERE  hudson.triggers.SafeTimerTask#run: Timer task com.cloudbees.jenkins.Cleaner@7ed56677 failed
java.lang.NoSuchMethodError: java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
        at hudson.Util.rawEncode(Util.java:886)
        at hudson.model.AbstractItem.getShortUrl(AbstractItem.java:576)
        at hudson.model.AbstractItem.getUrl(AbstractItem.java:537)

I don't know why there is a difference in behavior.  I don't know if the issue is related to something in my local environment, the Docker image definition that I'm using, or something completely different.

The folders which fail to open are different in the two instances, but the stack traces seem to consistently be associated with CharBuffer.rewind().

Later in the stack trace, it reports:

Caused by: java.lang.NoSuchMethodError: java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
	at hudson.Util.rawEncode(Util.java:886)

Duplicating the problem:

If others would like to duplicate the problem, they can try the following steps:
  1. Install git large file support on your Linux computer (or download from git-lfs.github.com)
  2. Iniitalize git lfs with
    $ git lfs install
    Git LFS initialized.
  3. Clone my docker-lfs repository
    $ git clone https://github.com/MarkEWaite/docker-lfs
    Cloning into 'docker-lfs'...
    Resolving deltas: 100% (12717/12717), done.
  4. Change to the docker-lfs directory
    $ cd docker-lfs
  5. Checkout the lts-with-plugins-rc branch
    $ git checkout -b lts-with-plugins-rc -t origin/lts-with-plugins-rc
    Filtering content: 100% (190/190), 244.87 MiB | 5.36 MiB/s, done.
    Branch 'lts-with-plugins-rc' set up to track remote branch 'lts-with-plugins-rc' from 'origin'.
    Switched to a new branch 'lts-with-plugins-rc'
  6. Build the docker image
    $ docker build -f Dockerfile -t markewaite/lts-rc:2.204.3 .
  7. Run the docker image
    $ docker run --rm -i -e JENKINS_ADVERTISED_HOSTNAME=`hostname` -e START_QUIET=True -p 8080:8080 -t markewaite/lts-rc:2.204.3
  8. Connect to the running image with a web browser
    $ python -m webbrowser http://$(hostname):8080/
  9.  Open each of the folders at the root of that Jenkins server.  One of them will fail to an Oops screen (at least does on the 3 machines where I've tested) 

End of symptoms, switching to wild, unjustified speculation:

There is mention on the jetty project and on stackoverflow that code compiled with JDK 9 or later may fail in this way when running with Java 8.  I'm running Java 8 in both the failure cases.  References:

Was the Jenkins 2.204.3 release candidate compiled with Java 11?

Thanks!
Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ee0962f2-b082-4b0e-a7ec-e832a69274fd%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.204.3 LTS RC testing started

Mark Waite-2


On Saturday, February 15, 2020 at 10:29:06 AM UTC-7, Mark Waite wrote:


On Friday, February 14, 2020 at 5:05:22 AM UTC-7, ogondza wrote:
Hello everyone,

Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-02-26.

Please, report your findings in this thread.


I've encountered a problem on my Jenkins test instances that are running the 2.204.3 release candidate inside Docker.  Some of the folders fail to open when I click them and I receive the following stack track in an "Oops" page on one instance:

org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.204.3-SNAPSHOT.jar!/hudson/model/View/index.jelly:42:43: <st:include> org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.204.3-SNAPSHOT.jar!/lib/hudson/projectView.jelly:84:48: <j:forEach> java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
	at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)

In the other test instance, the message appears in the console log and does not appear in the Jenkins Oops page.  In the console log, it reports:

2020-02-15 16:37:04.540+0000 [id=164374]        INFO    j.b.MultiBranchProject$BranchIndexing#run: Bugs-Pipeline-Checks/jenkins-bugs-multibranch-pipeline-bitbucket #20200215.093700 branch indexing action completed: SUCCESS in 3.6 sec
2020-02-15 16:39:26.329+0000 [id=39]    SEVERE  hudson.triggers.SafeTimerTask#run: Timer task com.cloudbees.jenkins.Cleaner@7ed56677 failed
java.lang.NoSuchMethodError: java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
        at hudson.Util.rawEncode(Util.java:886)
        at hudson.model.AbstractItem.getShortUrl(AbstractItem.java:576)
        at hudson.model.AbstractItem.getUrl(AbstractItem.java:537)

I don't know why there is a difference in behavior.  I don't know if the issue is related to something in my local environment, the Docker image definition that I'm using, or something completely different.


Same message appears when trying to evaluate reverse proxy setup for the reverse proxy administrative monitor.  It reports:

2020-02-15 17:34:13.223+0000 [id=144]   WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://debian9-a.markwaite.net:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test
java.lang.NoSuchMethodError: java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
        at hudson.Util.rawEncode(Util.java:886)
        at hudson.diagnosis.ReverseProxySetupMonitor.doTest(ReverseProxySetupMonitor.java:69)
        at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
        at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
Caused: java.lang.reflect.InvocationTargetException
        at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400)


 
The folders which fail to open are different in the two instances, but the stack traces seem to consistently be associated with CharBuffer.rewind().

Later in the stack trace, it reports:

Caused by: java.lang.NoSuchMethodError: java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
	at hudson.Util.rawEncode(Util.java:886)

Duplicating the problem:

If others would like to duplicate the problem, they can try the following steps:
  1. Install <a href="https://github.com/git-lfs/git-lfs/wiki/Installation" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fgit-lfs%2Fgit-lfs%2Fwiki%2FInstallation\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEErG-s6_OL7ofBeYewEZv9ARjxUQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fgit-lfs%2Fgit-lfs%2Fwiki%2FInstallation\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEErG-s6_OL7ofBeYewEZv9ARjxUQ&#39;;return true;">git large file support on your Linux computer (or download from <a href="http://git-lfs.github.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgit-lfs.github.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE0Mx8QkuBAjGmsb9VjruxBzBhyVQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgit-lfs.github.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE0Mx8QkuBAjGmsb9VjruxBzBhyVQ&#39;;return true;">git-lfs.github.com)
  2. Iniitalize git lfs with
    $ git lfs install
    Git LFS initialized.
  3. Clone my docker-lfs repository
    $ git clone <a href="https://github.com/MarkEWaite/docker-lfs" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FMarkEWaite%2Fdocker-lfs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEQw2B1gYmLytrMZwOehNlDUGzHng&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FMarkEWaite%2Fdocker-lfs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEQw2B1gYmLytrMZwOehNlDUGzHng&#39;;return true;">https://github.com/MarkEWaite/docker-lfs
    Cloning into 'docker-lfs'...
    Resolving deltas: 100% (12717/12717), done.
  4. Change to the docker-lfs directory
    $ cd docker-lfs
  5. Checkout the lts-with-plugins-rc branch
    $ git checkout -b lts-with-plugins-rc -t origin/lts-with-plugins-rc
    Filtering content: 100% (190/190), 244.87 MiB | 5.36 MiB/s, done.
    Branch 'lts-with-plugins-rc' set up to track remote branch 'lts-with-plugins-rc' from 'origin'.
    Switched to a new branch 'lts-with-plugins-rc'
  6. Build the docker image
    $ docker build -f Dockerfile -t markewaite/lts-rc:2.204.3 .
  7. Run the docker image
    $ docker run --rm -i -e JENKINS_ADVERTISED_HOSTNAME=`hostname` -e START_QUIET=True -p 8080:8080 -t markewaite/lts-rc:2.204.3
  8. Connect to the running image with a web browser
    $ python -m webbrowser http://$(hostname):8080/
  9.  Open each of the folders at the root of that Jenkins server.  One of them will fail to an Oops screen (at least does on the 3 machines where I've tested) 

End of symptoms, switching to wild, unjustified speculation:

There is mention on the jetty project and on stackoverflow that code compiled with JDK 9 or later may fail in this way when running with Java 8.  I'm running Java 8 in both the failure cases.  References:

  • <a href="https://github.com/eclipse/jetty.project/issues/3244" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Feclipse%2Fjetty.project%2Fissues%2F3244\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHNFBe_DnnG3e8nt0HmOa9p9GHz7w&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Feclipse%2Fjetty.project%2Fissues%2F3244\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHNFBe_DnnG3e8nt0HmOa9p9GHz7w&#39;;return true;">https://github.com/eclipse/jetty.project/issues/3244
  • <a href="https://stackoverflow.com/questions/48693695/java-nio-buffer-not-loading-clear-method-on-runtime" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F48693695%2Fjava-nio-buffer-not-loading-clear-method-on-runtime\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEu_ZVs9yyVqeAAexlO_THZOsdd7w&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F48693695%2Fjava-nio-buffer-not-loading-clear-method-on-runtime\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEu_ZVs9yyVqeAAexlO_THZOsdd7w&#39;;return true;">https://stackoverflow.com/questions/48693695/java-nio-buffer-not-loading-clear-method-on-runtime
Was the Jenkins 2.204.3 release candidate compiled with Java 11?

Thanks!
Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4c4a2ec1-2ec1-40d2-b955-98a4a21b1d1e%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.204.3 LTS RC testing started

Mark Waite-2


On Saturday, February 15, 2020 at 10:36:10 AM UTC-7, Mark Waite wrote:


On Saturday, February 15, 2020 at 10:29:06 AM UTC-7, Mark Waite wrote:


On Friday, February 14, 2020 at 5:05:22 AM UTC-7, ogondza wrote:
Hello everyone,

Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-02-26.

Please, report your findings in this thread.


I've encountered a problem on my Jenkins test instances that are running the 2.204.3 release candidate inside Docker.  Some of the folders fail to open when I click them and I receive the following stack track in an "Oops" page on one instance:

org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.204.3-SNAPSHOT.jar!/hudson/model/View/index.jelly:42:43: <st:include> org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.204.3-SNAPSHOT.jar!/lib/hudson/projectView.jelly:84:48: <j:forEach> java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
	at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)

In the other test instance, the message appears in the console log and does not appear in the Jenkins Oops page.  In the console log, it reports:

2020-02-15 16:37:04.540+0000 [id=164374]        INFO    j.b.MultiBranchProject$BranchIndexing#run: Bugs-Pipeline-Checks/jenkins-bugs-multibranch-pipeline-bitbucket #20200215.093700 branch indexing action completed: SUCCESS in 3.6 sec
2020-02-15 16:39:26.329+0000 [id=39]    SEVERE  hudson.triggers.SafeTimerTask#run: Timer task com.cloudbees.jenkins.Cleaner@7ed56677 failed
java.lang.NoSuchMethodError: java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
        at hudson.Util.rawEncode(Util.java:886)
        at hudson.model.AbstractItem.getShortUrl(AbstractItem.java:576)
        at hudson.model.AbstractItem.getUrl(AbstractItem.java:537)

I don't know why there is a difference in behavior.  I don't know if the issue is related to something in my local environment, the Docker image definition that I'm using, or something completely different.


Same message appears when trying to evaluate reverse proxy setup for the reverse proxy administrative monitor.  It reports:

2020-02-15 17:34:13.223+0000 [id=144]   WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving <a href="http://debian9-a.markwaite.net:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fdebian9-a.markwaite.net%3A8080%2FadministrativeMonitor%2Fhudson.diagnosis.ReverseProxySetupMonitor%2Ftest\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6xBjLpoR2SaWNdhPhK9RVYxxAvA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fdebian9-a.markwaite.net%3A8080%2FadministrativeMonitor%2Fhudson.diagnosis.ReverseProxySetupMonitor%2Ftest\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6xBjLpoR2SaWNdhPhK9RVYxxAvA&#39;;return true;">http://debian9-a.markwaite.net:8080/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test
java.lang.NoSuchMethodError: java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
        at hudson.Util.rawEncode(Util.java:886)
        at hudson.diagnosis.ReverseProxySetupMonitor.doTest(ReverseProxySetupMonitor.java:69)
        at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
        at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
Caused: java.lang.reflect.InvocationTargetException
        at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400)



Message does not appear if I configure the Docker image to use JDK 11 instead of JDK 8.

Replace the branch name "lts-with-plugins-rc" with "lts-jdk11-with-plugins-rc" to see the JDK 11 based configuration.

Mark Waite
 
 
The folders which fail to open are different in the two instances, but the stack traces seem to consistently be associated with CharBuffer.rewind().

Later in the stack trace, it reports:

Caused by: java.lang.NoSuchMethodError: java.nio.CharBuffer.rewind()Ljava/nio/CharBuffer;
	at hudson.Util.rawEncode(Util.java:886)

Duplicating the problem:

If others would like to duplicate the problem, they can try the following steps:
  1. Install <a href="https://github.com/git-lfs/git-lfs/wiki/Installation" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fgit-lfs%2Fgit-lfs%2Fwiki%2FInstallation\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEErG-s6_OL7ofBeYewEZv9ARjxUQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fgit-lfs%2Fgit-lfs%2Fwiki%2FInstallation\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEErG-s6_OL7ofBeYewEZv9ARjxUQ&#39;;return true;">git large file support on your Linux computer (or download from <a href="http://git-lfs.github.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgit-lfs.github.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE0Mx8QkuBAjGmsb9VjruxBzBhyVQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fgit-lfs.github.com\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE0Mx8QkuBAjGmsb9VjruxBzBhyVQ&#39;;return true;">git-lfs.github.com)
  2. Iniitalize git lfs with
    $ git lfs install
    Git LFS initialized.
  3. Clone my docker-lfs repository
    $ git clone <a href="https://github.com/MarkEWaite/docker-lfs" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FMarkEWaite%2Fdocker-lfs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEQw2B1gYmLytrMZwOehNlDUGzHng&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FMarkEWaite%2Fdocker-lfs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEQw2B1gYmLytrMZwOehNlDUGzHng&#39;;return true;">https://github.com/MarkEWaite/docker-lfs
    Cloning into 'docker-lfs'...
    Resolving deltas: 100% (12717/12717), done.
  4. Change to the docker-lfs directory
    $ cd docker-lfs
  5. Checkout the lts-with-plugins-rc branch
    $ git checkout -b lts-with-plugins-rc -t origin/lts-with-plugins-rc
    Filtering content: 100% (190/190), 244.87 MiB | 5.36 MiB/s, done.
    Branch 'lts-with-plugins-rc' set up to track remote branch 'lts-with-plugins-rc' from 'origin'.
    Switched to a new branch 'lts-with-plugins-rc'
  6. Build the docker image
    $ docker build -f Dockerfile -t markewaite/lts-rc:2.204.3 .
  7. Run the docker image
    $ docker run --rm -i -e JENKINS_ADVERTISED_HOSTNAME=`hostname` -e START_QUIET=True -p 8080:8080 -t markewaite/lts-rc:2.204.3
  8. Connect to the running image with a web browser
    $ python -m webbrowser http://$(hostname):8080/
  9.  Open each of the folders at the root of that Jenkins server.  One of them will fail to an Oops screen (at least does on the 3 machines where I've tested) 

End of symptoms, switching to wild, unjustified speculation:

There is mention on the jetty project and on stackoverflow that code compiled with JDK 9 or later may fail in this way when running with Java 8.  I'm running Java 8 in both the failure cases.  References:

  • <a href="https://github.com/eclipse/jetty.project/issues/3244" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Feclipse%2Fjetty.project%2Fissues%2F3244\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHNFBe_DnnG3e8nt0HmOa9p9GHz7w&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Feclipse%2Fjetty.project%2Fissues%2F3244\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHNFBe_DnnG3e8nt0HmOa9p9GHz7w&#39;;return true;">https://github.com/eclipse/jetty.project/issues/3244
  • <a href="https://stackoverflow.com/questions/48693695/java-nio-buffer-not-loading-clear-method-on-runtime" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F48693695%2Fjava-nio-buffer-not-loading-clear-method-on-runtime\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEu_ZVs9yyVqeAAexlO_THZOsdd7w&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F48693695%2Fjava-nio-buffer-not-loading-clear-method-on-runtime\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEu_ZVs9yyVqeAAexlO_THZOsdd7w&#39;;return true;">https://stackoverflow.com/questions/48693695/java-nio-buffer-not-loading-clear-method-on-runtime
Was the Jenkins 2.204.3 release candidate compiled with Java 11?

Thanks!
Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7bc502b9-4933-4910-9057-7541c33fcf8f%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.204.3 LTS RC testing started

Jesse Glick-4
Could you file this in JIRA please with the smallest steps to reproduce you have?

Does this occur in `master`?

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr32uF7ZCagBNJoRoEwW6GTWSvYDgp%2BMVyASWKmAHLePRw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.204.3 LTS RC testing started

Mark Waite-2

On Sun, Feb 16, 2020 at 7:29 AM Jesse Glick <[hidden email]> wrote:
Could you file this in JIRA please with the smallest steps to reproduce you have?


Yes, I've copied those steps into a Jira ticket.  I'm not aware of any of the steps that can be removed, so I believe those are the minimum steps to duplicate the issue.
 
Does this occur in `master`?

I don't know if it occurs with 'master'.  It does not occur with 2.204.2.  It does not occur with weekly 2.220 as downloaded from the official release site.  I'll build the master branch and try it later today.

I'll also try to confirm my suspicion that the root of the issue is that the release candidate build was compiled with Java 11 without specifically mandating '-release 8'  The links included in the earlier message seem to indicate that setting source and target are necessary but not sufficient for Java 11 to generate Java 8 byte code.

I've switched my testing of the release candidate to use Java 11 and that testing has found no issues. The problem does not occur when the same release candidate bits are run with Java 11.  It only happens with Java 8.
 
Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr32uF7ZCagBNJoRoEwW6GTWSvYDgp%2BMVyASWKmAHLePRw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGRSCWun%2BWncQ%3Dk9A38ioF1O73QojwhUkAaE-UNProDBg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.204.3 LTS RC testing started

Mark Waite-2


On Sunday, February 16, 2020 at 7:58:03 AM UTC-7, Mark Waite wrote:

On Sun, Feb 16, 2020 at 7:29 AM Jesse Glick wrote:
Could you file this in JIRA please with the smallest steps to reproduce you have?


Yes, I've copied those steps into a <a href="https://issues.jenkins-ci.org/browse/JENKINS-61105" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-61105\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHDy-L8vEZIKnEmA729f2J0uUFRsQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-61105\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHDy-L8vEZIKnEmA729f2J0uUFRsQ&#39;;return true;">Jira ticket.  I'm not aware of any of the steps that can be removed, so I believe those are the minimum steps to duplicate the issue.
 
Does this occur in `master`?

I don't know if it occurs with 'master'.  It does not occur with 2.204.2.  It does not occur with weekly 2.220 as downloaded from the official release site.  I'll build the master branch and try it later today.

I'll also try to confirm my suspicion that the root of the issue is that the release candidate build was compiled with Java 11 without specifically mandating '-release 8'  The links included in the earlier message seem to indicate that setting source and target are necessary but not sufficient for Java 11 to generate Java 8 byte code.


I've compared the manifest from Jenkins 2.204.2 with the manifest from Jenkins 2.204.3 rc.  The key difference appears to be:

Jenkins 2.204.2: Build-Jdk-Spec: 1.8

Jenkins 2.204.3 rc: Build-Jdk-Spec: 11

I think we need a rebuild of the 2.204.3 release candidate using JDK 8.

Mark Waite
 
I've switched my testing of the release candidate to use Java 11 and that testing has found no issues. The problem does not occur when the same release candidate bits are run with Java 11.  It only happens with Java 8.
 
Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/736b81e6-10cf-4762-95cb-4cfe4aacecfd%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.204.3 LTS RC testing started

Oliver Gondža-2
In reply to this post by Oliver Gondža-2
Mark, thanks for reporting this. I have published an RC respin[1] with Java 8, until we identify the reason why is this causing problems.

Please make sure the ongoing testing is done with ca01d0bf523d6752f54277ca4c91feef0d60acc75c42d65f65bbefe09f9e8e69 (sha256). Thanks!

[1] http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war

--
oliver

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/005cb301-b149-44b4-bf3a-25dbd5ca35dd%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.204.3 LTS RC testing started

Mark Waite-2
Thanks!  Any idea how long the propagation delay is through the mirrors?  I tried to download the URL you provided http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war and the sha245sum that I see is still the original, not the new one that you provided.

On Mon, Feb 17, 2020 at 5:09 AM ogondza <[hidden email]> wrote:
Mark, thanks for reporting this. I have published an RC respin[1] with Java 8, until we identify the reason why is this causing problems.

Please make sure the ongoing testing is done with ca01d0bf523d6752f54277ca4c91feef0d60acc75c42d65f65bbefe09f9e8e69 (sha256). Thanks!


--
oliver

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/005cb301-b149-44b4-bf3a-25dbd5ca35dd%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGY783zJoVQXbz3xpa7j-bmh3nnrY20ThQYU660STX9zg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Jenkins 2.204.3 LTS RC testing started

Oliver Gondža-2
Propagating new file usually takes about an hour or two (never really
measured), so I can only guess propagating an update takes about the
same amount of time.

On 17/02/2020 13.23, Mark Waite wrote:

> Thanks!  Any idea how long the propagation delay is through the
> mirrors?  I tried to download the URL you provided
> http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war and the
> sha245sum that I see is still the original, not the new one that you
> provided.
>
> On Mon, Feb 17, 2020 at 5:09 AM ogondza <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Mark, thanks for reporting this. I have published an RC respin[1]
>     with Java 8, until we identify the reason why is this causing problems.
>
>     Please make sure the ongoing testing is done with
>     ca01d0bf523d6752f54277ca4c91feef0d60acc75c42d65f65bbefe09f9e8e69
>     (sha256). Thanks!
>
>     [1] http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war
>
>     --
>     oliver
>
>     --
>     You received this message because you are subscribed to the Google
>     Groups "Jenkins Developers" group.
>     To unsubscribe from this group and stop receiving emails from it,
>     send an email to [hidden email]
>     <mailto:[hidden email]>.
>     To view this discussion on the web visit
>     https://groups.google.com/d/msgid/jenkinsci-dev/005cb301-b149-44b4-bf3a-25dbd5ca35dd%40googlegroups.com
>     <https://groups.google.com/d/msgid/jenkinsci-dev/005cb301-b149-44b4-bf3a-25dbd5ca35dd%40googlegroups.com?utm_medium=email&utm_source=footer>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [hidden email]
> <mailto:[hidden email]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGY783zJoVQXbz3xpa7j-bmh3nnrY20ThQYU660STX9zg%40mail.gmail.com 
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGY783zJoVQXbz3xpa7j-bmh3nnrY20ThQYU660STX9zg%40mail.gmail.com?utm_medium=email&utm_source=footer>.


--
oliver

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/86c961e2-c861-c4a6-80e0-fd60b70e15b5%40gmail.com.