You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

End user instructions

What is changed and why?

  • During update on TDS-XXX builds behaviour is quite changed.
  • Artifactory cannot handle build permissions properly
  • Previously builds were renamed from buildName into repoName-buildName,we handle it automatically by us but this feature produced some bugs.
  •  So we decided remove this feature

What does it mean to me?

  • Previously renamed build will not be renamed.
  • It means that instead of repoName-buildName build will be called buildName.
  • If buildName already exist, then new version will be created.

How I should create build properly?

  • Think twice how you call build, especially if you are using shared instance. If two independent projects will create build with same name, builds will be merged into one.
    Renaming build works same as creating new one, action from oper. team will be required. (Recreating permissions)
  • Run job and create build.

  • Next step will differ by used artifactory

    I am using project specific Artifactory instanceI am using shared Artifactory instance
    • If build is visible, no special action needed.
    • If build is not visible to you, then create ticket {oper. team should fill how}
    • Newly created build will be invisible to anybody except system administators.
    • As next create ticket {oper. team should fill how} and oper team will create build
      permission target for you.

Do I need create ticket after each build run?

  • No, if build permission already was created, it used for every next build version automatically.
  • Please remember that renaming build is for artifactory same as creating new one which means that ticket will have to be create.

Oper team instructions 

Shared vs project artifactory instances

Upgrade steps

How to create permissions

  • No labels