Build failed in Jenkins: UIMA-DUCC #1601

[Apache Jenkins Server]

See 

Changes:

[burn] UIMA-6124 Many small changes simplifying the DuccHead master/backup 
determination

--
[...truncated 394.21 MB...]
[INFO] 
[INFO] --- maven-changes-plugin:2.12.1:jira-report (default-cli) @ uima-ducc ---
[INFO] 
[INFO] --- maven-resources-plugin:3.1.0:copy-resources 
(readme-releasenotes-version-replace) @ uima-ducc ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] 
[INFO] --- cobertura-maven-plugin:2.7:instrument (default-cli) @ uima-ducc ---
[INFO] Skipping cobertura mojo for project with packaging type 'pom'
[INFO] 
[INFO] <<< cobertura-maven-plugin:2.7:cobertura (default-cli) < [cobertura]test 
@ uima-ducc <<<
[INFO] 
[INFO] --- cobertura-maven-plugin:2.7:cobertura (default-cli) @ uima-ducc ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache UIMA DUCC: uima-ducc-parent . SUCCESS [01:36 min]
[INFO] Apache UIMA DUCC: uima-ducc-workitem-v2  SUCCESS [02:07 min]
[INFO] Apache UIMA DUCC: uima-ducc-user ... SUCCESS [01:50 min]
[INFO] Apache UIMA DUCC: uima-ducc-common . SUCCESS [02:22 min]
[INFO] Apache UIMA DUCC: uima-ducc-pullservice  SUCCESS [08:38 min]
[INFO] Apache UIMA DUCC: uima-ducc-container .. SUCCESS [02:28 min]
[INFO] Apache UIMA DUCC: uima-ducc-transport .. SUCCESS [02:15 min]
[INFO] Apache UIMA DUCC: uima-ducc-cli  SUCCESS [01:31 min]
[INFO] Apache UIMA DUCC: uima-ducc-pm . SUCCESS [ 59.254 s]
[INFO] Apache UIMA DUCC: uima-ducc-rm . SUCCESS [01:23 min]
[INFO] Apache UIMA DUCC: uima-ducc-sm . SUCCESS [01:17 min]
[INFO] Apache UIMA DUCC: uima-ducc-database ... SUCCESS [01:21 min]
[INFO] Apache UIMA DUCC: uima-ducc-orchestrator ... SUCCESS [01:42 min]
[INFO] Apache UIMA DUCC: uima-ducc-agent .. SUCCESS [01:40 min]
[INFO] Apache UIMA DUCC: uima-ducc-duccdocs ... SUCCESS [ 28.410 s]
[INFO] Apache UIMA DUCC: uima-ducc-web  SUCCESS [02:40 min]
[INFO] Apache UIMA DUCC: uima-ducc-examples ... SUCCESS [01:16 min]
[INFO] Apache UIMA DUCC: uima-ducc-spawn .. SUCCESS [ 25.171 s]
[INFO] Apache UIMA DUCC: uima-ducc-workitem-v3  SUCCESS [ 45.186 s]
[INFO] Apache UIMA-DUCC: uima-ducc  SUCCESS [02:19 min]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 41:13 min
[INFO] Finished at: 2019-09-06T00:56:04+00:00
[INFO] Final Memory: 218M/1399M
[INFO] 
[JENKINS] Archiving 
 to 
org.apache.uima/uima-ducc-sm/3.0.1-SNAPSHOT/uima-ducc-sm-3.0.1-SNAPSHOT.pom
[JENKINS] Archiving 

 to org.apache.uima/uima-ducc-sm/3.0.1-SNAPSHOT/uima-ducc-sm-3.0.1-SNAPSHOT.jar
[JENKINS] Archiving 
 to 
org.apache.uima/uima-ducc-parent/3.0.1-SNAPSHOT/uima-ducc-parent-3.0.1-SNAPSHOT.pom
[JENKINS] Archiving 
 
to 
org.apache.uima/uima-ducc-duccdocs/3.0.1-SNAPSHOT/uima-ducc-duccdocs-3.0.1-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.uima/uima-ducc-pullservice/3.0.1-SNAPSHOT/uima-ducc-pullservice-3.0.1-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.uima/uima-ducc-pullservice/3.0.1-SNAPSHOT/uima-ducc-pullservice-3.0.1-SNAPSHOT.jar
[JENKINS] Archiving 
 to 
org.apache.uima/uima-ducc-pm/3.0.1-SNAPSHOT/uima-ducc-pm-3.0.1-SNAPSHOT.pom
[JENKINS] Archiving 

 to org.apache.uima/uima-ducc-pm/3.0.1-SNAPSHOT/uima-ducc-pm-3.0.1-SNAPSHOT.jar
[JENKINS] Archiving 
 
to 
org.apache.uima/uima-ducc-database/3.0.1-SNAPSHOT/uima-ducc-database-3.0.1-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.uima/uima-ducc-database/3.0.1-SNAPSHOT/uima-ducc-database-3.0.1-SNAPSHOT.jar
[JENKINS] Archiving 

[jira] [Created] (UIMA-6124) Simplify master/backup determination for reliable DUCC

[Burn Lewis (Jira)]

Burn Lewis created UIMA-6124:


 Summary: Simplify master/backup determination for reliable DUCC
 Key: UIMA-6124
 URL: https://issues.apache.org/jira/browse/UIMA-6124
 Project: UIMA
  Issue Type: Improvement
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
 Fix For: future-DUCC


Replace the multiple DuccHead classes by one that checks if a reliable 
installation & if a head node is active.  Simplify scripts by not checking if 
the Keepalived configuration is consistent with the head node declarations.  
Allow a single-node DB to be auto-managed by the master head node.  Get the 
(first part of) the current node name via python from ducc_base's 
self.localhost rather than running /bin/hostname.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Re: Setting up some branching conventions?

[Marshall Schor]

I've asked about this on INFRA.

I've looked at some active projects, like couchDB, and they don't seem to be
using this naming convention.

-M

On 9/5/2019 1:24 PM, Richard Eckart de Castilho wrote:
> On 5. Sep 2019, at 17:58, Marshall Schor  wrote:
>> I think it's a good convention to have bugfix/1234-ShortSummary and
>> feature/1234-shortSummary, so I suggest we follow that.
>>
>> I'm not quite ready to allocate the master-v2 to be (just) a maintenance 
>> branch,
>> but will probably get there..
> INFRA said that "rel" is a branch/tag prefix which they usually protect.
>
> So I guess that might be a common convention for releases/maintenance 
> branches.
>
> -- Richard

starting some uima website pages for git

[Marshall Schor]

I added 3 pages:

a git page which just has nav links to:

a page on git conventions

a page on steps to convert a project to git


This is a work-in progress :-)...

-Marshall

Re: Setting up some branching conventions?

[Richard Eckart de Castilho]

On 5. Sep 2019, at 17:58, Marshall Schor  wrote:
> 
> I think it's a good convention to have bugfix/1234-ShortSummary and
> feature/1234-shortSummary, so I suggest we follow that.
> 
> I'm not quite ready to allocate the master-v2 to be (just) a maintenance 
> branch,
> but will probably get there..

INFRA said that "rel" is a branch/tag prefix which they usually protect.

So I guess that might be a common convention for releases/maintenance branches.

-- Richard

Re: Setting up some branching conventions?

[Marshall Schor]

I think it's a good convention to have bugfix/1234-ShortSummary and
feature/1234-shortSummary, so I suggest we follow that.

I'm not quite ready to allocate the master-v2 to be (just) a maintenance branch,
but will probably get there..


On 9/4/2019 11:32 AM, Richard Eckart de Castilho wrote:
> On 3. Sep 2019, at 23:12, Marshall Schor  wrote:
>> I'm not sure about the value of this; it feels more complex, and the benefits
>> are not clear to me.
> Besides being able to bulk-protected all branches with a common prefix
> (using some "XXX/*" pattern), graphical git clients also have a habit
> of using the slashes in branch name to organize them into folders.
> Thus it makes it easier to find a certain branch if there is a naming 
> convention.
>
> I have also learned/adopted such conventions more recently, but I find them 
> useful
> as they nicely organize things and help me to find them.
>
> The convention I have learned is to use "feature" to mark feature branches and
> "bugfix" to mark bug fix branches, also to include the issue ID in the branch 
> name
> and the description, e.g. (fictional)
>
>   bugfix/1323-NPE-being-thrown-on-close-button
>   feature/4213-Add-profile-icons
>
> Cheers,
>
> -- Richard

filing an INFRA jira to rename uima-uimaj branch "trunk" -> "master"

[Marshall Schor]

https://issues.apache.org/jira/browse/INFRA-18988

also protect branch master-v2

Re: Git protection for uima-uimaj

[Marshall Schor]

I asked on infra list, if the protections were the same for both GitHub and
gitbox.a.o, and the answer was "yes".

-Marshall

On 9/4/2019 5:01 PM, Marshall Schor wrote:
> On the asf infra slack channel, I asked about protection for uima-uimaj
> branches, what was set, how to see, etc.
>
> The answer was:
>
 right now, nothing, which is actually an oversight on my part. i need to 
 go protect
> the master branch.
 protect = refs/heads/trunk refs/heads/master refs/heads/rel/ refs/tags/rel/
 that is the default protection
> Protection appears to be a property of GitHub, not of "git" itself (the ProGit
> book has no hits for this kind of protection).
>
> I cannot find  this syntax anywhere.  Does anyone know what this refers to?
>
> Also, when branches are "protected" in github, you have to additionally 
> specify
> the kinds of protection.  Does anyone know what these are?  I feel like I'm
> missing some significant documentation ...
>
> Cheers. -Marshall
>
>
>