Jump to content


Question about %serverport% trigger var change in 2014.1

2014.1 serverport trigger

  • Please log in to reply
2 replies to this topic

#1 Bruce Mc

Bruce Mc

    Advanced Member

  • Members
  • PipPipPip
  • 84 posts
  • LocationSeattle Area

Posted 08 April 2014 - 09:15 PM

I'm reviewing the release notes for 2014.1 and I noticed the text describing change level 770301 has this text,

The %serverport% trigger variable now includes a transport prefix
(eg, "ssl:", "tcp6:", or "ssl6:"). Thus "p4 -p %serverport%"
can be used to connect to the server whether or not the server
listens on IPv4 or IPv6, with or without SSL.

The 2014.1 System Admin's guide has this description about the %serverport% var.

The transport, IP address and port of the Perforce server, in the format prefix:ip_address:port.

If we are using tcp4 will the var have the format ip_address:port? Is it safe to assume that when tcp4 is used there will not be a leading colon?

We parse the %serverport% var's value with a perl regex in several of our triggers and want to be make sure the regex is constructed properly.

Thanks,

Bruce M

#2 P4Matt

P4Matt

    Advanced Member

  • Members
  • PipPipPip
  • 1383 posts

Posted 10 April 2014 - 04:45 AM

I just tested and even if the user specifies tcp4: it gets stripped.

#3 Bruce Mc

Bruce Mc

    Advanced Member

  • Members
  • PipPipPip
  • 84 posts
  • LocationSeattle Area

Posted 10 April 2014 - 04:37 PM

Thanks Matt.





Also tagged with one or more of these keywords: 2014.1, serverport, trigger

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users