DevOps Toolchains migration for NON-US applications: please facilitate accessing to Toolchains entries list even from NON-US region....
Dear Support. I did tried to make the upgrade to all my projects several weeks ago. I lately discovered that some of them failed.
Then I did made troubleshooting and tried to fix the errors that did not allow the deployment in the Toolchain environment. Once fixed the errors, as you said in developer works, I did want to try once again the upgrade process BUT, I could not do it because an entry in the Toolchain repository for that application already exists.
So I did search on HOW to delete that. BUT, the explanation in the documentation was not applicable because that application was in UK non in US, then the Toolchain service is not available in UK.
Fortunately I do have some application that I successfully upgraded and I could access to the Toolchains list and then I was able to delete all the entries that went in error the first time.
I would suggest to make much more easy accessing to the Toolchains entries list even from ouside US region.... Thanks. Claudio.
Dear Claudio,
Thank you for the feedback. Please let me know if you need further help in upgrading your JazzHub projects to toolchains. If so, please share the JazzHub project URL and any issues you are facing with the toolchain that was created as part of the upgrade process.
Sorry about the issues had in deleting toolchains. Just a clarification that, in order to delete the toolchain, you don't have to delete the application (that was deployed by the toolchain).
Thanks
Dear Pradeep, thank you very much for your prompt response. Just to let you know that the delete button in the Toolchains DO NOT fully works, it still leave the repository in the Bluemix Git Repository. So, when you want to try again the upgrade it will not allow you to proceed due to the existance of the repository there. AND, the "Existing" label that the hoover tool tip suggest to select does not exists.... This means that you have to go to your Repos in the Bluemix git and removed it manually.
Actually the development team should be advised because this is a bug. Claudio.
NOW I do have a serious problem: I had a chance to successful run again the upgrade process BUT my repository in the Bluemix Git is EMPTY !!! Why? Because the second time you do the upgrade Bluemix try to clone getting the code from git.ng.bluemix.net AND NOT from the Jazz platform. Looks like that "reverting" as the documentation suggest using the Toolchains delete process, DO NOT revert the original Git Repository (Jazz hub), where the code, fortunately still exists.
Here is the log of the git.ng.bluemix.net activities for that project.
Command line instructions
Git global setup
git config --global user.name "CLAUDIO FADDA"
git config --global user.email "claudio_fadda@it.ibm.com"
Create a new repository
git clone git@git.ng.bluemix.net:claudio_fadda/HelloWorldByClaudio.git
cd HelloWorldByClaudio
touch README.md
git add README.md
git commit -m "add README"
git push -u origin master
Existing folder
cd existing_folder
git init
git remote add origin git@git.ng.bluemix.net:claudio_fadda/HelloWorldByClaudio.git
git add .
git commit
git push -u origin master
Existing Git repository
cd existing_repo
git remote add origin git@git.ng.bluemix.net:claudio_fadda/HelloWorldByClaudio.git
git push -u origin --all
git push -u origin --tags
Dear Claudio,
Let me reassure you that the upgrade process will always take the data from the JazzHub repository. The behavior you are seeing during your second upgrade attempt is probably due to the fact that the import of source code from JazzHub to your new repo (created as part of second upgrade) failed for some reason. In that case the whole upgrade process is considered as a failure and the status of the JazzHub project will be set to "Ready to Upgrade".
I can confirm this from the log for the upgrade operation you did around 9:45AM Eastern time.
Could you please confirm the banner on your JazzHub project overview page? It will have the link "upgrade now".
Thanks
Dear Pradeep, sorry for getting back just now, I didn't check it out during the weekend. Let me recap a little bit what I'm facing. Some weeks ago I started the upgrade process of all my projects. Some of them went at the first shot, some of them are still there. For the first a took for a problem determination I did opened a dw Question and came up that there was something very old in the environment, in fact if I tried to make a deployment with the JazzHub environment it did fails. I fix the issues that were related to old version of node.js module. Then I did try last week to apply the same type of fixes to the HelloWorldByClaudio project. I looked at the package.json file. I updated all the obsolete node.js modules. I made a deployment using the old JazzHub evironment. The application strated. Then I tried to run the upgrade. I got and empty git repository. So I cloned the empty project. Then I copied the original code in my Eclipse environment and push everything to the server. And now I have the code there, but I lost the git history (that BTW is still in the JazzHub repo). Then I thought that could be that I did left enough time to the infrastructure to copy hundreds of bytes. So I tried to do the same with HistologicalAnalyzer project. This time I made exactly everything as the process's asking. Clicked on the "upgrade now" link and wait. From the Bluemix side it looks that everything is fine:
But the git IS EMPTY !!!!!
And I'm still having the same link.
Please help.
Hi Claudio, Sorry about that. I noticed that you had tried to upgrade HistologicalAnalyzer on May 19 Friday at around 1:30pm Eastern Time. The log also has some errors, which I believe should not happen again.
Could you please try upgrading HistologicalAnalyzer once again?