I'm setting up a CI process in Ignition 8.1 Perspective to push changes from Ignition to an Azure DevOps repository branch

I'm setting up a CI process in Ignition 8.1 Perspective to push changes from Ignition to an Azure DevOps repository branch. Here's what I've done so far:

  1. Installed the Git-1.0.0 module to enable Git functionality in Ignition Designer. following this document (ignition-git-module/git-designer/pom.xml at 6e3f3cb4135ba47223439acad23ad780363f02df · AXONE-IO/ignition-git-module · GitHub)
  2. Added the HTTPS Azure DevOps repository URL for the Dev branch in Ignition by navigating to Git -> Project -> Edit, pasting the repository URL, and saving the changes.
  3. Generated a Personal Access Token (PAT) in Azure DevOps.
  4. Created a new user in Azure DevOps by going to More -> Manage User, adding my username in "Ignition User," and pasting the PAT in the "User Name" field. I didn't provide a password or confirm password since I'm using a PAT. I saved the changes by clicking "Create New User."
  5. In Ignition Designer, after making changes and saving them, I tried to commit the changes, but encountered an error when trying to pull changes, saying "Cannot invoke 'String.toCharArray()' because 'password' is null."

I've attached screenshots for reference.

Could someone please help me troubleshoot this issue? I'd also appreciate guidance on integrating Azure DevOps with Ignition for CICD. Thank you in advance!

please find the attachments:


CreatedUserForLoginInIgnitionDesignerWithUserNamePassword

I don't have any git ignition module experience but i have ADO experience.

One possible suggestion: I know it is a bit counter-intuitive to the normal use of the PAT token, but perhaps try putting the PAT token as the password and use the username as the username. I suggest this because it is possible that this git module isn't handling the PAT Token the same way other git clients would normally? So instead of

  1. PAT
  2. NULL
  3. NULL

do

1.ADO USER
2.PAT
3.PAT

you could also try this

  1. git
  2. PAT
  3. PAT

or

  1. null
  2. PAT
  3. PAT

In your step 4, I am a little confused.. Why do you need to create a new user in Azure Dev Ops after you have made a PAT Token? Maybe I misunderstand this; Did you mean in the gateway settings portal and not ADO?

Thank you for your prompt response. I appreciate the guidance provided. Just to clarify, there seems to be a misunderstanding. I'm not creating a new user in Azure DevOps. Instead, I'm creating a user in the Ignition gateway. I apologize for any confusion. I will try the suggested solution and let you know how it goes. Thank you again for your assistance.

I hope the suggestion helps... I don't know if it will work :slight_smile:

I've attempted the suggested solutions, but encountered errors with each configuration:

When using the

  1. ADO USER
  2. PTA
    3.PTA
    settings, Ignition Designer displays the following error message: "org.eclipse.jgit.api.errors.RefNotAdvertisedException: Remote origin did not advise Ref for branch master. This Ref may not exist in the remote or may be hidden by permission setting."

When using the

  1. NULL
  2. PTA
  3. PTA
    settings Ignition Designer throws the error: "org.eclipse.jgit.api.errors.TransportException: https://ttlmes.VisualStudio.com/Tenneco/_git/Ignition: not authorized."

Trying the solution where I input the PAT for all three fields, I still encounter the error: **




**

I would greatly appreciate any further assistance you can provide in resolving these issues. Thank you for your patience and support.