• Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor

      hi can anyone help plz

      Jenkins ver. 2.150.3 

      i cant not create any new maven with git project anymore not even copy from the old one

      cuz in SCM git Credentials didn't work right anymore 

      i dont know what's wrong by now

      UPDATED even i specified the Repository URL the Credentials still showERROR

      at old jenkins(plugins )version i think this is not a problem

      my git is same as jenkins server on and for save download time i use  localhost to get much more faster git download speed from 10 minutes down to 30 seconds

      i donw know why the old unrestricted can not be use in the localhost ?

      BTW chinese language is not complete

       

      these are my credentials account infos

      THIS OLD MAVEN PROJECT WITH GIT CAN STILL WORK 

       

       

          [JENKINS-56192] Cannot run project when using Git SCM

          Oleg Nenashev added a comment - - edited

          I am not sure what is the request here. Your repository URL is not specified. The Credentials list will be empty if all credentials are scoped to domains and users.

          W.r.t the localization, CC surenpi

           

          Oleg Nenashev added a comment - - edited I am not sure what is the request here. Your repository URL is not specified. The Credentials list will be empty if all credentials are scoped to domains and users. W.r.t the localization, CC surenpi  

          blank hang added a comment - - edited

          Credentials that should be available irrespective of domain specification to requirements matching.

          i think the Credentials list should always show because i need use it in manyway. i dont think should limit that. 

          blank hang added a comment - - edited Credentials that should be available irrespective of domain specification to requirements matching. i think the Credentials list should always show because i need use it in manyway. i dont think should limit that. 

          blank hang added a comment -

          after using localhost:3000 instead of localhost it works again

           

          blank hang added a comment - after using localhost:3000 instead of localhost it works again  

            blankhang blank hang
            blankhang blank hang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: