-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14-04-18 02:04 PM, John Meinel wrote: > I did eventually manage to run the CI tests, though there are some > oddities:
Sorry about that. The top-level 'upgrade-job' and 'deploy-job' scripts were never meant to run locally. Originally, we entered these commands as configuration parameters in Jenkins, and then we extracted them to scripts to ensure they were consistent across different substrates and different Jenkins deploys. But please try the deploy_stack.py script. It is much more user-friendly. It takes options and arguments, not env variables. > 2) You have to set LOCAL_JENKINS_URL to the ec2 instance That was because on Canonistack, instances can't access their own public IP addresses. We might be able to get rid of that now that we're on EC2, but we'd still need JENKINS_URL. > 3) You have to set WORKSPACE, but you *also* have to have $PWD > already be in WORKSPACE. Per Jenkins. > 4) If you made a mistake with $PWD it also has the nice properties > of rm * -rf, which wipes out wherever you were running it. Unfortunately, Jenkins doesn't have the option of starting with a clean workspace. > 5) Even though I've set JUJU_HOME to $HOME/dev/juju-ci/cloud-city, > the first thing it does is override JUJU_HOME with $HOME/cloud-city > (or for manual source $HOME/cloud-city/ec2rc.) Sure. This is needed on Jenkins, and we do it here so we don't have to do it in every job configuration. I think it would be fine to change it to only override JUJU_HOME if unset. > 7) It uses a special SSH key which comes in cloud-city. But by > default the file is rw-rw... which is too open for SSH to let you > use the key. This is an unfortunate consequence of managing cloud-city with Bazaar, which doesn't support full unix permissions. > You can probably change the environments.yaml to a) not include a > key, or b) include your own key, or c) ssh-add the existing SSH key > from cloud-city. Really, cloud-city is only if you need to use our credentials. If you're not trying to use our credentials, then you wouldn't need it. Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTUoXHAAoJEK84cMOcf+9hXfUH/AqS5BMgvDcMEPp/JWJI0KTD kgsNCpaH0LtDEyyE8kbz0c167EOzauKpw31+YKbBEeORElbMbnsiycnx0HMTso1B hzSVjeamK7S1woST87c0eLg+mJLW0ufQoFWnWsZ9TrAEpFYl8bOCn51viiPM7WF2 1sRJ09WgoJQZmxKTsQA8BE3XwWfwokoWhSkzmLCESrzcYLpFJZz+Lc6i3JTl88/K sZWS1jLiaZbPVfbksBwhYJW5w2xtuciK8lgru2iJ/y8Tp4NStDSOSTKomUf3Xusv kCHLm+IM610nxydnN9hRkOiYEHDE7jTQ6FcHGk2unr71LPsyPR6J3YtJ9N2fNbU= =DHBU -----END PGP SIGNATURE----- -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
