Hi,
Using iTop 3.0, I would like to know if anyone know if it's possible to integrate CI/CD on iTop ?
I'm new about iTop and learning the entire process. I would use Jenkins or Gocd to configure this, but there is any ressources on forums. The idea would be to be able to make the new module integration process completly automatic. I already find the iTop Toolkit script which execute the update of the code and the db, but as I said, I don't even know if it's possible because I found anything about the subject.
Thanks a lot for your help !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm looking for the same, I'm creating a CI/CD pipeline to automate as much as possible the development cycle on our iTop instances. I found on your GitHub repository a test folder that, if I'm not mistaken, doesn't come in the zip uploaded to SourceForge. I have played with the test.php class and launched some tests from the browser, but I couldn't find documentation about it so I don't know if this folder is just for internal use, if we have to figure it out on our own or if I'm missing something.
On another note, in the Code tab in SourceForge you guys offer a "git clone" command, but it clones the latest version and I would like to stay on the latest LTS, so 2.7.7 at the moment. If i wanted to clone your repository, is it safe to deploy it to production or is it a development repository? I'm asking specifically about this repository.
I have to document the process anyways, so I wouldn't mind sharing it in this forum when I'm done. I'm using GitLab CI/CD tools, I mention it because I think that you guys are using Jenkins, so I think it would be nice to have the process documented on multiple tools.
Thanks in advance!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Our PHPUnit tests aren't part of the packages indeed as the later are meant for deployment on various environments including production ones.
The iTop GitHub repository contains the core code, including the tests and some other stuff (like dev tools).
We don't recommend to clone this repository and use it anywhere else than on a dev environment, even if checking out a specific tag. What I said before about the tests files is also right for other files. And plus this repository doesn't contains all of the code available in the community package (for 2.7.7 you won't get the webhook extension for example).
We are not planning on documenting how to build a CI on top of iTop.
Our clients get access to the ITSM Designer which is a great help for creating iTop customizations, and also access to the support team which will assist on any migration (from analyzing the customizations before migration to having the prod env migrated). Our partners who write extensions also gets access to our migration help services.
Those services aren't free.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Using iTop 3.0, I would like to know if anyone know if it's possible to integrate CI/CD on iTop ?
I'm new about iTop and learning the entire process. I would use Jenkins or Gocd to configure this, but there is any ressources on forums. The idea would be to be able to make the new module integration process completly automatic. I already find the iTop Toolkit script which execute the update of the code and the db, but as I said, I don't even know if it's possible because I found anything about the subject.
Thanks a lot for your help !
Hello,
What do you mean integrate ? Are you willing to deploy iTop automatically ?
Hello,
I'm looking for the same, I'm creating a CI/CD pipeline to automate as much as possible the development cycle on our iTop instances. I found on your GitHub repository a test folder that, if I'm not mistaken, doesn't come in the zip uploaded to SourceForge. I have played with the test.php class and launched some tests from the browser, but I couldn't find documentation about it so I don't know if this folder is just for internal use, if we have to figure it out on our own or if I'm missing something.
On another note, in the Code tab in SourceForge you guys offer a "git clone" command, but it clones the latest version and I would like to stay on the latest LTS, so 2.7.7 at the moment. If i wanted to clone your repository, is it safe to deploy it to production or is it a development repository? I'm asking specifically about this repository.
I have to document the process anyways, so I wouldn't mind sharing it in this forum when I'm done. I'm using GitLab CI/CD tools, I mention it because I think that you guys are using Jenkins, so I think it would be nice to have the process documented on multiple tools.
Thanks in advance!
Hello,
Our PHPUnit tests aren't part of the packages indeed as the later are meant for deployment on various environments including production ones.
The iTop GitHub repository contains the core code, including the tests and some other stuff (like dev tools).
We don't recommend to clone this repository and use it anywhere else than on a dev environment, even if checking out a specific tag. What I said before about the tests files is also right for other files. And plus this repository doesn't contains all of the code available in the community package (for 2.7.7 you won't get the webhook extension for example).
We are not planning on documenting how to build a CI on top of iTop.
Our clients get access to the ITSM Designer which is a great help for creating iTop customizations, and also access to the support team which will assist on any migration (from analyzing the customizations before migration to having the prod env migrated). Our partners who write extensions also gets access to our migration help services.
Those services aren't free.