| Hi Jim, 
 We were solving that problem within Jersey release and we were
      told by people from Eclipse Foundation that bots do not require
      ECA signed. So we referenced to that in PR's comment and approved
      that. Take a look for example at
      https://github.com/eclipse-ee4j/jersey/pull/4186. There is comment
      from Jan Supol there which states that EF bots do not require ECA
      signed. similar issue is here:
      https://github.com/eclipse-ee4j/jersey/pull/4052 
 Regards, Maxim
 On 23. 08. 19 15:43, Jim Krueger wrote:
 
      
        
          Thanks Maxim,   That makes sense.    I've hit another
            problem though that maybe somebody else on this mailing list
            has hit? 
 
          
          
            
              Hi Jim, Basically the idea is that the job prepares release
                branch and tag and commits them to Github. However it's
                difficult to create PR directly from job, so it is left
                for manual processing. So, after job is done it is
                required to submit PR with merge request to master for
                release branch. After PR is accepted (PR is merged into
                master), the release branch shall be deleted. And the
                release tag remains in Github. 
 Regards, Maxim
 On
                22. 08. 19 13:04, Jim Krueger wrote:
 
                
                  Thanks Maxim,  
 I came to the same realization yesterday.  The IP
                    address was added to the known-hosts file so that
                    message is no longer in my logs.   However, that is
                    no longer my question.   The reason I was concerned
                    about this in the first place is that I realized
                    that the POM.xml changes made in release job are not
                    being automatically committed to master by any
                    Jenkins job.   This is true for other components as
                    well.   So my question now is if it is expected that
                    the POM changes made in the release job and
                    committed to the release branch in github should be
                    automatically merged with master in some Jenkins job
                    or if this is something individual component owners
                    are supposed to do manually later?   Thanks
 
 
                  
                  
                    
                      _______________________________________________Hi Jim, jakarta-stable bot connects to Github just
                        fine. The message you see in the log ( Failed to add the RSA host key for IP address '140.82.114.3' to the list of known hosts (/home/jenkins/.ssh/known_hosts). ) is not about a connection failure, it states
                        only that bot is not able to add (in general
                        write to) file /home/jenkins/.ssh/known_hosts.
                        But it does not fail push to github. Which
                        successfully passed and you have release branch
                        created: https://github.com/eclipse-ee4j/jaxr-api/tree/1.0.10-BRANCH
 Tag is created as well. The message you are referring to (Failed to add
                        the RSA host key for IP address '140.82.114.3'
                        to the list of known hosts
                        (/home/jenkins/.ssh/known_hosts).) is basically
                        normal for all release jobs. For some reason
                        bots are not allowed to add/write anything to
                        known_hosts. But this does not affect any job's
                        functionality. 
 Regards, Maxim
 On
                        21. 08. 19 18:44, Jim Krueger wrote:
 
                        
                          Correction:   I'm not sure if the message
                            I asked about above is actually affecting
                            anything meaningful.   I was thinking that
                            the Jenkins release jobs would be committing
                            the POM.xml changes to Master and I wasn't
                            seeing those commits.  Upon further review
                            of the script I see that the POM.xml changes
                            are only pushed to the created branch (ie.
                            1.0.10-BRANCH).    This appears to be what
                            is being done in other components as well
                            (such as JCA). 
 So the question I have now is
                                this:  "When/where are the
                            changes in these release-specific branches
                            merged to master and by whom?". 
 Thanks
 
 
                          
                          
                            
                            
 
                              
                              
                                
                                  You should file a bug in BugZilla
                                    for Eclipse Webmasters. 
 -- Dmitry 
 ------ Исходное сообщение ------ Отправлено: 21.08.2019 16:54:51 Тема: Jakarta Stable release
                                    Jenkins jobs unable to access github 
 
                                    
                                      
                                        Hi, The Release jobs in Jenkins
                                          for the Jakarta Stable APIs
                                          are running successfully (on
                                          the surface), however the
                                          github commits and PRs to
                                          update the POM files are not
                                          running successfully. 
 
                                          + echo '-[ Push branch and tag to GitHub ]----------------------------------------------'
-[ Push branch and tag to GitHub ]----------------------------------------------
+ git push origin 1.0.10-BRANCH
Failed to add the RSA host key for IP address '140.82.114.3' to the list of known hosts (/home/jenkins/.ssh/known_hosts).
remote: 
remote: Create a pull request for '1.0.10-BRANCH' on GitHub by visiting:        
remote:      https://github.com/eclipse-ee4j/jaxr-api/pull/new/1.0.10-BRANCH        
remote: 
To github.com:eclipse-ee4j/jaxr-api.git
 * [new branch]      1.0.10-BRANCH -> 1.0.10-BRANCH
+ git push origin 1.0.10
Failed to add the RSA host key for IP address '140.82.114.3' to the list of known hosts (/home/jenkins/.ssh/known_hosts).
To github.com:eclipse-ee4j/jaxr-api.git
 I'm assuming some authority needs to be granted.   Thanks
 
 _______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.eclipse.org_mailman_listinfo_ee4j-2Dbuild&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=FI7G3fqPHeI5hydbLLyMWMUDxAvHLuc51cQABHON-A0&m=_UIiiytM_gG_VvnSVzrLw9_Mvm8l50_Emv4Q6nyBeF8&s=X9yZ-jOEF0c1Rh8YuqrycxHqGgtM-1DFONN78ubGec0&e= 
 ee4j-build mailing list
 ee4j-build@xxxxxxxxxxx
 To change your delivery options, retrieve your
                    password, or unsubscribe from this list, visit
 https://www.eclipse.org/mailman/listinfo/ee4j-build
 
 |