Exercise 05: Publishing Problems

What This Exercise Is About

Having a successful build is only the first part of the release engineering experience. Consistently publishing your builds every week is part of good project health, and doing so in an automated fashion is important for good release engineer health.

There are many things that can go wrong. This lab will explore several of those.

What You Should Be Able To Do

At the end of the lab, you should be able to:

Identify several ways to fix build promotion problems
Know where to go for help
Know where to contribute lessons learned

Required Materials

Eclipse 3.4M5
Eclipse Modeling Framework (EMF) 2.4M5

Exercise Instructions

This exercise is carried out entirely using the Eclipse Software Development Kit (SDK) version 3.4M5 with the Eclipse Modeling Framework (EMF) 2.4M5 installed into it. The exercise instructions refer to this product as either Eclipse or as "the workbench."

These instructions are located in your workspace, in the Build_Workshop/Exercise05_PublishingProblems folder.

Directions

Step A: Explore failures

Switch to the Plug-in Development perspective, if not already there.

Select Window -> Open Perspective -> Other... -> Plug-in Development.

For each of the following scenarios, there will be two pieces of information to review:
1. Build log -- note the error message that is produced
2. Resolution -- what to do to fix the problem
There are five scenarios to explore below.

Properties file promoteToEclipse.*.properties not found

cvs server: cannot find module `org.eclipse.m2t/org.eclipse.jet.releng/promoteToEclipse.jet.properties' - ignored
cvs [export aborted]: cannot expand modules
[promote] Properties file org.eclipse.m2t/org.eclipse.jet.releng/promoteToEclipse.jet.properties not found in CVS for branch/tag R0_9_maintenance. Exiting...

TODO: When building from a new branch, don't forget to branch your .releng project and update your promoteToEclipse.*.properties file!

Permission denied creating target directories

[promote] [19:40:03] Create target drop folder .../0.9.0/I200803111920 on remote box started:
Not allowed to do 'mkdir' at /usr/bin/cvssh line 106.

TODO: Ensure that your build is running as a user with full bash shell access to download1.eclipse.org and dev.eclipse.org

Uploaded files corrupted enroute, mirror/node replication glitch

[compare] Directory sizes do not match! Compare failed.
[compare] Local sizes (in bytes):
  1 75 78 78 79 80 87 128 2183 3302 5415 12231 19522 21754 32349 66129 72883 141574 265130 311318 911547 2753418 4502034
[compare] Remote sizes (in bytes):

[promote] [19:40:04] ERROR! Script exiting with code 2 from compareFolders.sh

TODO: Upload again using ./promoteToEclipse.sh ... -droponly

Host key verification failed

```
Host key verification failed.
```
TODO: Because a promote runs from the web as the web user, it must connect to the build user in order to run the script. You need to manually log in as the web user, then connect to the buildUser@buildServer & productionUser@productionServer via ssh in order to put this key in place:
```
$ ssh build@buildbox
	$ sudo -u www-data bash
		$ ssh build@buildbox
		$ exit
		$ ssh build@prodbox
		$ exit
	$ exit
	$ ssh build@buildbox
	$ exit
	$ ssh build@prodbox
	$ exit
$ exit
```
You need to also authorize the build user to connect to the build server and the production server:
```
$ ssh build@buildbox
	$ ssh build@buildbox
	$ exit
	$ ssh build@prodbox
	$ exit
$ exit
```
See also Releasing - SSH Key Setup.

Permission denied - SSH authentication failure

Permission denied, please try again.
Permission denied, please try again.
Received disconnect from 127.0.0.1: 2: Too many authentication failures for build

TODO: Grant passwordless permission for the web user and the build user to ssh to the build user. To do so, copy the ssh key from each of those users into the build user's ~/.ssh/authorized_keys file.
See also Releasing - SSH Key Setup.

Summary

You have learned how to diagnose and repair several build problems. For even more examples, see:

Modeling Project Releng - Releasing

If you encounter any other problems not listed here or in the wiki, please don't hesitate to contribute your experiences and your tips, to help your fellow release engineers and Eclipse.