Infrastructure
  1. Infrastructure
  2. INFRA-7738

Need openjpa docs buildbot enhanced to support new 2.3.x stream

    Details

    • Type: Task Task
    • Status: Waiting for Infra
    • Priority: Major Major
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Buildbot
    • Labels:

      Description

      We have a new service stream (branch) for OpenJPA called 2.3.x. We need to perform the doc builds like we have for the other streams. The team member (Albert) that originally set this up with Infra is no longer on the team, so I'm trying to figure out the process.

      It looks like I have access to the openjpa.conf file. So, should I go ahead and make the necessary update? Here's all that I was planning to do (adding '2.3.x'):

      ojpa_branches = ['trunk' , '2.3.x' , '2.2.1.x' , '2.2.x' , '2.1.x' , '2.0.x' , '1.3.x' , '1.2.x' , '1.0.x']

      The thing I'm not sure about is how to go about testing this change. I like to do the test-then-commit process... :-) Thanks for any assistance.

      I was also having some issues with IRC and the #openjpa-bot channel last night, but I'll keep experimenting with that.

        Issue Links

          Activity

          Hide
          Kevin Sutter added a comment -
          Hi Gavin,
          I looked at the log you provided, but which errors are you wondering about... :-) I see several error/warning messages and I'm not sure which ones are critical to your question.

          I see these, but I have no idea what they are referring to...

          [ERROR] VM #image: error : too few arguments to macro. Wanted 5 got 0
          [ERROR] VM #image: error : too few arguments to macro. Wanted 5 got 0
          [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0
          [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0

          And, then I saw a set of messages similar to this one. Although this sounds bad and is repeated for every OpenJPA doc module, since it was ignored, does it really affect the build?

          [ERROR] Error fetching link: /home/buildslave2/slave2/openjpa-trunk-docs/build/openjpa-kernel/target/apidocs/package-list. Ignored it.

          And, then I found this one, which is probably the one you were referring to...

          [ERROR] Failed to execute goal com.agilejava.docbkx:docbkx-maven-plugin:2.0.13:generate-pdf (build-pdf-doc) on project apache-openjpa: Execution build-pdf-doc of goal com.agilejava.docbkx:docbkx-maven-plugin:2.0.13:generate-pdf failed: Plugin com.agilejava.docbkx:docbkx-maven-plugin:2.0.13 or one of its dependencies could not be resolved: The following artifacts could not be resolved: com.sun:jai_core:jar:1.1.3, com.sun:jai_codec:jar:1.1.3: Could not find artifact com.sun:jai_core:jar:1.1.3 in agilejava (http://agilejava.com/maven) -> [Help 1]

          Not being able to generate the pdf is an issue.

          Sorry that I'm not much more help on this... I just don't understand what has changed to prevent our doc builds from working. And, since these logs are from the 2.4.0-SNAPSHOT builds, my guess is that none of our doc builds are working currently. The intent of this JIRA was to get the 2.3.x stream working, but now trunk isn't working either? According to this status, we've had an issue with trunk doc builds since Aug 12...

          http://ci.apache.org/builders/openjpa-trunk-docs

          Thanks for your help in trying to resolve this mess!
          Show
          Kevin Sutter added a comment - Hi Gavin, I looked at the log you provided, but which errors are you wondering about... :-) I see several error/warning messages and I'm not sure which ones are critical to your question. I see these, but I have no idea what they are referring to... [ERROR] VM #image: error : too few arguments to macro. Wanted 5 got 0 [ERROR] VM #image: error : too few arguments to macro. Wanted 5 got 0 [ERROR] VM #displayTree: error : too few arguments to macro. Wanted 2 got 0 [ERROR] VM #menuItem: error : too few arguments to macro. Wanted 1 got 0 And, then I saw a set of messages similar to this one. Although this sounds bad and is repeated for every OpenJPA doc module, since it was ignored, does it really affect the build? [ERROR] Error fetching link: /home/buildslave2/slave2/openjpa-trunk-docs/build/openjpa-kernel/target/apidocs/package-list. Ignored it. And, then I found this one, which is probably the one you were referring to... [ERROR] Failed to execute goal com.agilejava.docbkx:docbkx-maven-plugin:2.0.13:generate-pdf (build-pdf-doc) on project apache-openjpa: Execution build-pdf-doc of goal com.agilejava.docbkx:docbkx-maven-plugin:2.0.13:generate-pdf failed: Plugin com.agilejava.docbkx:docbkx-maven-plugin:2.0.13 or one of its dependencies could not be resolved: The following artifacts could not be resolved: com.sun:jai_core:jar:1.1.3, com.sun:jai_codec:jar:1.1.3: Could not find artifact com.sun:jai_core:jar:1.1.3 in agilejava ( http://agilejava.com/maven ) -> [Help 1] Not being able to generate the pdf is an issue. Sorry that I'm not much more help on this... I just don't understand what has changed to prevent our doc builds from working. And, since these logs are from the 2.4.0-SNAPSHOT builds, my guess is that none of our doc builds are working currently. The intent of this JIRA was to get the 2.3.x stream working, but now trunk isn't working either? According to this status, we've had an issue with trunk doc builds since Aug 12... http://ci.apache.org/builders/openjpa-trunk-docs Thanks for your help in trying to resolve this mess!
          Hide
          Gavin added a comment -
          Hi [~kwsutter] I got further (with sacrifices we talk about later.)

          In the meantime please look at :

          http://ci.apache.org/builders/openjpa-trunk-docs/builds/75/steps/compile/logs/stdio

          and see if this is an error your side or ours.

          Thanks!
          Show
          Gavin added a comment - Hi [~kwsutter] I got further (with sacrifices we talk about later.) In the meantime please look at : http://ci.apache.org/builders/openjpa-trunk-docs/builds/75/steps/compile/logs/stdio and see if this is an error your side or ours. Thanks!
          Hide
          Gavin added a comment -
          I'll take a look over the next couple of days Kevin.
          Thanks.
          Show
          Gavin added a comment - I'll take a look over the next couple of days Kevin. Thanks.
          Hide
          Kevin Sutter added a comment -
          Any progress on this JIRA, Gavin? I'm not sure what else I can do at this point. Thanks!
          Show
          Kevin Sutter added a comment - Any progress on this JIRA, Gavin? I'm not sure what else I can do at this point. Thanks!
          Hide
          Gavin added a comment -
          Basically why they fail is that the Buildbot Master is checking for the existence of the file paths mentioned (on the master).
          So the configcheck fails.

          We need to work out what has changed between buildbot 0.8.5 and 0.8.8 to cause this behaviour as it did work on the old version.

          We'll therfore likley need to find a different way of expressing what we want to happen.
          I'll take a first look shortly.

          And yes, I did realise that it was the meat of the script :)

          Show
          Gavin added a comment - Basically why they fail is that the Buildbot Master is checking for the existence of the file paths mentioned (on the master). So the configcheck fails. We need to work out what has changed between buildbot 0.8.5 and 0.8.8 to cause this behaviour as it did work on the old version. We'll therfore likley need to find a different way of expressing what we want to happen. I'll take a first look shortly. And yes, I did realise that it was the meat of the script :)
          Hide
          Kevin Sutter added a comment -
          Okay, so I took a look at the ### comments in the openjpa.conf file and I have no idea what is wrong... :-) I can now see that without these blocks of script, then basically this openjpa-bot build is not doing a heck of a lot. That is, this is the meat of the script. But, I have no idea on why these blocks stopped working or what might be needed to re-enabled them. Any assistance would be most appreciated. I'm willing to learn something new, but I need some pointers on where to start. Thanks.
          Show
          Kevin Sutter added a comment - Okay, so I took a look at the ### comments in the openjpa.conf file and I have no idea what is wrong... :-) I can now see that without these blocks of script, then basically this openjpa-bot build is not doing a heck of a lot. That is, this is the meat of the script. But, I have no idea on why these blocks stopped working or what might be needed to re-enabled them. Any assistance would be most appreciated. I'm willing to learn something new, but I need some pointers on where to start. Thanks.
          Hide
          Kevin Sutter added a comment -
          Thanks, Gavin. I now see the openjpa-bot active and responsive to irc requests. Question... As I work through the commented out sections of the conf file, how should I test this? Is there anyway to "unit test" the changes? Or, is it trial-and-error with the real bot? Thanks!
          Show
          Kevin Sutter added a comment - Thanks, Gavin. I now see the openjpa-bot active and responsive to irc requests. Question... As I work through the commented out sections of the conf file, how should I test this? Is there anyway to "unit test" the changes? Or, is it trial-and-error with the real bot? Thanks!
          Hide
          Gavin added a comment -
          Let me know please if you need a hand with re-enabling the commented code blocks.
          Show
          Gavin added a comment - Let me know please if you need a hand with re-enabling the commented code blocks.
          Hide
          Gavin added a comment -
          Note that successful updates - i.e. those that do not break the config - autoupdate and go live within 5 minutes. failures will result in no code being changed on the server and a failure email will go to infrastructure@apache.org

          Show
          Gavin added a comment - Note that successful updates - i.e. those that do not break the config - autoupdate and go live within 5 minutes. failures will result in no code being changed on the server and a failure email will go to infrastructure@apache.org
          Hide
          Kevin Sutter added a comment -
          Okay, I updated the openjpa.conf for the 2.3.x branch. I'm not exactly clear on the impact of the blocks of script that you commented out, but let's see where this takes us. Thanks!
          Show
          Kevin Sutter added a comment - Okay, I updated the openjpa.conf for the 2.3.x branch. I'm not exactly clear on the impact of the blocks of script that you commented out, but let's see where this takes us. Thanks!
          Hide
          Gavin added a comment -
          Feel free to update the openjpa.conf file (update your wc first)

          Note that to get the buildbot config to pass I commented out a chunk of code in your file that needs to be investigated further.
          Show
          Gavin added a comment - Feel free to update the openjpa.conf file (update your wc first) Note that to get the buildbot config to pass I commented out a chunk of code in your file that needs to be investigated further.

            People

            • Assignee:
              Gavin
              Reporter:
              Kevin Sutter
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Development