Jump to content

mig

Administrators
  • Content count

    60
  • Joined

  • Last visited

  • Days Won

    2

mig last won the day on April 21 2016

mig had the most liked content!

Community Reputation

3 Neutral

About mig

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,994 profile views
  1. Connection Problem to Jira via SSL

    Hi trx, Glad to hear that! Unfortunately our extensions don't currently support TLSv1.1 or higher, as you finally found out. We'll need to bump up our .NET Framework verson to make it possible. Regarding the URL bug, I'll talk to the development team so we can fix it as soon as possible. Sorry for the inconvenience! Thanks for your feedback! Regards, Miguel
  2. Connection Problem to Jira via SSL

    That's weird, it's the same request used by our JIRA extension. I understood that this is only reproduced when clicking the "Test connection" button, right? Could you click the "accept" button to save that configuration (as we think it should be working), restart Plastic SCM and see if it does as expected? I mean, it retrieves issue titles from JIRA, the branch explorer lists the associated issues to branches, the "Create Branch" dialog shows the pending tasks list... If it doesn't, please share the session log with us so we can continue figuring out what might be wrong. Regards, Miguel
  3. Connection Problem to Jira via SSL

    Hi, Can you perform a GET request against https://yourserver:443/jira/rest/api/2/status using the "Authorization: Basic <username>:<password-in-base64>" header, and share the results with us? Thank you! Regards, Miguel
  4. Connection Problem to Jira via SSL

    Hi trx, Could you attach the complete client log for that session and the jira.conf configuration file contents? You'll need to remove the security data before sharing it with us, of course. Thank you! Regards, Miguel
  5. no tree view(version 5.4.16.198)

    You're welcome! I'm glad it worked out for you. Thanks for your feedback! Regards, Miguel
  6. no tree view(version 5.4.16.198)

    Hi ramesh, Do you mean that it's difficult for you to go and select just the changes under a specific directory when there are hundreds of changed files, or is it just that you're not finding the changes you expected in the pending changes view? If you're looking for a more efficient way to check in only the files under a particular directory, please have in mind that you can filter the results in the pending changes view through the filter entry in the top right corner: just type in the directory path or name so you can narrow down the amount of results. If the expected changes don't appear in the pending changes tree, could you give us more details on your issue? Steps to reproduce it, workspace structure, whether you have a ignored.conf/hidden_changes.conf file, etc. Thank you! Regards, Miguel
  7. Hi karmakat, How is your Plastic SCM client configured? Are you using the SSL protocol? If that's the case, are you using a valid certificate? Could you attach the output of a 'cm lrep' command? Could you also describe to us your current workspace structure so that we can try to reproduce your issue? Thank you! Regards, Miguel
  8. Plastic issue tracking missing on Linux

    Hi crychair, Our JIRA extension doesn't make JIRA display any information regarding the Plastic SCM branch linked to each particular task at the moment. Besides the information stored after each checkin, that is. The 'Task on branch' working mode applies only to how the Plastic SCM client displays task information in its views. The JIRA extension (or any other Plastic SCM issue tracker extension) only works as an adapter to retrieve information from the issue tracker so it can be displayed on the Plastic SCM client, and additionally perform some actions using the issue tracker remote API. If you'd like to see your workflow implemented in our extension system you can propose it in our UserVoice website and see if it gets enough traction! https://plasticscm.uservoice.com/forums/15467-general Regards, Miguel
  9. Hi karmakat, Could you share the response body you're getting with those errors? That could give us more information on what's going on. Additionally, could you configure the plasticAPI logging? You'd just need to create a file called 'plasticapi.log.conf' in the client binaries directory with this content: <log4net> <appender name="RollingFileAppender" type="log4net.Appender.RollingFileAppender"> <file value="plasticapi.client.log" /> <!-- change this value to any path you want --> <appendToFile value="true" /> <rollingStyle value="Size" /> <maxSizeRollBackups value="5" /> <maximumFileSize value="10MB" /> <staticLogFileName value="true" /> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%date %username %-5level %logger - %message%newline" /> </layout> </appender> <root> <level value="DEBUG" /> <appender-ref ref="RollingFileAppender" /> </root> </log4net> That will create a file called plasticapi.client.log in the client binaries directory, so make sure you have permissions to write in that path or change it in the marked <file> tag. Please run the requests again and share the output and the generated log file with us. Thank you! Regards, Miguel
  10. Hi Tiju, I just checked CentOS 7 and Fedora 25 and I was able to successfully install Plastic SCM in both distros following the instructions available in our website. No issues or errors were raised. Could you give us more details about your setup? Which OS are you targeting? Could you attach the console output of the command or the yum log (available at /var/log/yum.log)?
  11. A few Linux problems

    Hi jeffpk, Just in case you wish to install Plastic SCM in an Ubuntu box in the future, I'm really happy to inform you that we've upgraded our repositories to be compatible with Ubuntu 16.04. That means you'll no longer need manually download and configure the software, as it'll be done by the package installers :-) Regards, Miguel
  12. Hello everyone! I'm really happy to inform you that we've upgraded our repositories to be compatible with Ubuntu 16.04 or later! The repository signatures now use digest algorithm SHA-256. Everything should be back to normal now. Regards, Miguel
  13. Hello everyone! I'm really happy to inform you that we've upgraded our repositories to be compatible with Ubuntu 16.04 or later! The repository signatures now use digest algorithm SHA-256. Everything should be back to normal now. Regards, Miguel
  14. Hi Engin, Yes, there will be no compatibility issues with 6.0 clients, so feel free to upgrade them and take advantage of the new features! Regards, Miguel
  15. Hi Engin, There are no version limitations regarding the client. The server, however, requires a different license to run version 6.0. It is automatically upgraded if your server has the auto-renewal token set and you have a subscription license (either monthly or yearly). If you have a perpetual license, please contact support! Regards, Miguel
×